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 Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs 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 Symantecs 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 [email protected] [email protected] [email protected]

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

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

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

16

Contents

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 .................................................................. Responding to alerts .................................................................. About using the Summary View for monitoring NetBackup alerts ................................................................................. Viewing alerts by severity ............................................................ Monitoring Audit Trails ............................................................... About Audit Trails ................................................................ About the Audit Trails report .................................................. About OpsCenter features for Audit Trails ................................ Managing Audit Trails settings ............................................... Monitoring Audit Trails .........................................................

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

Contents

17

Chapter 8

Managing NetBackup using Symantec OpsCenter .....................................................................

About the Manage views .............................................................. Controlling the scope of Manage views ........................................... About managing alert policies ....................................................... About OpsCenter alert policies ................................................ Viewing the details for a single alert policy ............................... Filtering on type of alert policy ............................................... About creating (or changing) an alert policy .............................. Managing an alert policy ....................................................... Viewing the alerts associated with an alert policy ....................... About managing NetBackup storage .............................................. Manage > Storage > Storage Unit view ..................................... Manage > Storage > Storage Unit Group view ............................ Manage > Storage > Storage Lifecycle Policy view ....................... About managing NetBackup devices ............................................... Manage > Devices > Drive view ............................................... Manage > Devices > Robot view ............................................... Manage > Devices > Disk Pool view .......................................... Manage > Devices > SAN Client view ........................................ Manage > Devices > FT Server view ......................................... About managing NetBackup Hosts ................................................. Managing Audit Trails settings ............................................... About managing NetBackup Deployment Analysis ............................ About Capacity License report ................................................ Compiling data for the report ................................................. Generating a Capacity Licensing report .................................... About possible Capacity License report issues ............................

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

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 ....................................................................... 545 546 547 547 549 549 549 550 551 552 552 552

18

Contents

Post-clone operations .................................................................. Troubleshooting Guided Recovery ................................................. Troubleshooting files for metadata collection operations at the time of the backup .......................................................... Troubleshooting files for Guided Recovery validation operations ..................................................................... Troubleshooting files for Guided Recovery cloning operations .....................................................................

552 553 553 554 554

Chapter 10

Understanding and configuring OpsCenter alerts ..............................................................................

About using SNMP with OpsCenter ................................................ About SNMP ........................................................................ About SNMP versions ............................................................ SNMP versions supported in OpsCenter .................................... About the Management Information Base (MIB) and OpsCenter support ......................................................................... SNMP traps ......................................................................... Alert descriptions in OpsCenter .............................................. Configuring the SNMP trap community name for OpsCenter ..................................................................... Configuring the SNMP version for sending SNMP traps ............... Alert configuration settings in OpsCenter ................................. Frequently asked SNMP and OpsCenter questions ...................... About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 ...................................................... About managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows ..............................................

557 557 558 558 559 559 559 562 574 575 576 577 577 578

Chapter 11

Reporting in OpsCenter .................................................... 579

About OpsCenter reports ............................................................. OpsCenter reports UI ............................................................ Report creation wizards in OpsCenter ...................................... Reports > Report Templates ................................................... About custom reports in OpsCenter ......................................... About custom SQL query in OpsCenter ..................................... Report Templates in OpsCenter ..................................................... About report filters in OpsCenter ............................................ Creating an OpsCenter report using a Report Template ............... About managing reports in OpsCenter ............................................ Save report and email report dialog boxes ................................. Saving an OpsCenter report .................................................... 579 580 581 581 582 582 583 584 585 586 586 588

Contents

19

Exporting an OpsCenter report ............................................... File formats available in OpsCenter .......................................... Emailing a report in OpsCenter ............................................... Adding email recipients to an OpsCenter report mailing .............. Add email recipients dialog box options .................................... Creating a custom report in OpsCenter ........................................... About OpsCenter report conditions .......................................... Creating an OpsCenter report using SQL query ................................ About managing My Reports ........................................................ Creating a report using the My Reports tab ............................... Deleting a saved report using the My Reports tab ....................... Viewing a saved report using the My Reports tab ........................ Editing a saved report using the My Reports tab ......................... Exporting a saved report ........................................................ Emailing a saved report ......................................................... About managing My Dashboard .................................................... Reports > My Dashboard options ............................................. Adding reports to a dashboard ................................................ Modifying a dashboard section ................................................ Deleting a dashboard section .................................................. Emailing dashboard sections .................................................. Refreshing My Dashboard ...................................................... About managing reports folders in OpsCenter ................................. Reports > Manage Folders options ........................................... Adding a reports folder in OpsCenter ....................................... Editing a reports folder in OpsCenter ....................................... Deleting reports folders in OpsCenter ...................................... Deleting reports from a folder in OpsCenter .............................. Using report schedules in OpsCenter .............................................. Reports > Schedules options ......................................................... About managing report schedules in OpsCenter ............................... Viewing report schedule details in OpsCenter ............................ Report Schedule Wizard ........................................................ Creating a report schedule in OpsCenter ................................... Editing a report schedule in OpsCenter ..................................... Deleting a report schedule in OpsCenter ................................... Enabling or disabling a report schedule .................................... About managing time schedules in OpsCenter ................................. Reports > Schedules > Create or Edit Time Schedule options ......................................................................... Viewing time schedule details ................................................. Creating a time schedule ........................................................ Editing a time schedule ..........................................................

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

20

Contents

Deleting a time schedule ........................................................ About Report Templates descriptions ............................................. About Enterprise Vault Archiving reports in OpsCenter ............... About Audit reports .............................................................. About Backup reports in OpsCenter ......................................... About Catalog reports in OpsCenter ......................................... About Chargeback reports in OpsCenter ................................... About Client reports in OpsCenter ........................................... About Disk and Tape Device Activity reports in OpsCenter .... 6 4 4 About Media reports in OpsCenter ........................................... About Performance reports in OpsCenter .................................. About Policy reports in OpsCenter ........................................... About Restore reports in OpsCenter ......................................... About Storage Lifecycle Policy reports ............................... Workload Analyzer ...............................................................

612 612 613 616 617 636 637 638

647 651 654 657 657 693

Appendix A

Additional information on PureDisk data collection ....................................................................... 703

About AT configuration scenarios specific to PureDisk backup product .............................................................................. About Scenario 1: Common Root Broker ................................... About Scenario 2: Different Root Brokers .................................. Setting up a trust between the OpsCenter AB host and PureDisk SPA host ................................................................................... 703 704 705 707

Appendix B Appendix C

Attributes of NetBackup data ......................................... 709

Backup data attributes ................................................................ 709

Man pages for CLIs ............................................................ 741

changeDbPassword ..................................................................... changeVxATProperties ................................................................ configurePorts ........................................................................... dbbackup .................................................................................. dbdefrag ................................................................................... opsadmin .................................................................................. opsCenterAgentSupport .............................................................. opsCenterSupport ...................................................................... runstoredquery .......................................................................... startagent ................................................................................. startdb ..................................................................................... 742 744 745 746 747 748 750 751 753 754 755

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

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

OpsCenters ability to forecast backup resource requirements helps data center executives to decide whether to maintain the existing resources or add new capacity. The detailed, drill-down OpsCenter reports help you determine the applications, databases, or business departments that are the heaviest consumers of backup resources. For example, in an environment running 20 instances of Oracle applications, you can generate a report showing resource consumption by department, server, or location. Depending on this information, organizations can provide appropriate resource planning in advance. Symantec OpsCenter Analytics offers you a set of chargeback reports that detail backup 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 exchanges 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 Administrators Guide for Windows, Volume I NetBackup Administrators 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

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.

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

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

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.

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.

Getting started using Symantec OpsCenter About starting the OpsCenter console

47

Table 1-2 Issue and Cause

OpsCenter console access issues, causes, and solution (continued) Solution

The OpsCenter Web interface is running, but the Use the following steps on Windows: OpsCenter console is not available. Your Web browser Locate the opscenter.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. INSTALL_PATH\OpsCenter\gui\webserver\webapps Verify that all the OpsCenter server services are running. 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.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, use the following command: /opt/SYMCOpsCenterServer/bin/opsadmin monitor Start all the OpsCenter Server processes by using the following commands: /opt/SYMCOpsCenterServer/bin/opsadmin.sh start

48

Getting started using Symantec OpsCenter About starting the OpsCenter console

Table 1-2 Issue and Cause

OpsCenter console access issues, causes, 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.0 and later versions. Open Internet Explorer . On the Tools menu, click Internet Options. Click the Security tab. Under Select a Web content zone to specify its security settings, click the Internet, icon and then 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: If you do not want to change your security settings,

you must manually append /opscenter to the OpsCenter URL. Without the changes to the security settings, the issue recurs every time that you accessOpsCenter, and you must add /opscenter to the URL.

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'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button and then click Search.

50

Getting started using Symantec OpsCenter About starting the OpsCenter console

Table 1-2 Issue and Cause

OpsCenter console access issues, causes, 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). Go to Tools > Folder Options > File Types Select Extension: "(NONE)" anf File Type: "URL:HyperText Transfer Protocol" Click Advanced. In the Edit File Type window, select Open and click Edit. Uncheck "Use DDE" (the dialog should then hide the lower part). Click OK for that dialog and the next one (afterwards, 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"

8 9

Note that the "File Types" user interface that allows you to uncheck the "Use DDE" option, as described above, is not available in Windows Vista, so you will need to edit the registry to remove the "ddeexec" key. 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).

Note: Editing the registry incorrectly can damage your

system. Do not attempt these steps if you are inexperienced or uncomfortable using the Registry Editor. 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):

Getting started using Symantec OpsCenter About starting the OpsCenter console

51

Table 1-2 Issue and Cause

OpsCenter console access issues, causes, and solution (continued) Solution 1 2 3 4

Go to Start > Run, then type regedit and click OK. Use the directory tree hierarchy to navigate to "HKEY_CLASSES_ROOT\HTTP\shell\open\ddeexec". Delete the "ddeexec" registry key. Repeat for "HKEY_CLASSES_ROOT\HTTPS\shell\open\ddeexec" (and any other protocols you want to fix). Repeat for "HKEY_CLASSES_ROOT\FirefoxURL\shell\open\ddeexec". Repeat for "HKEY_CLASSES_ROOT\FirefoxHTML\shell\open\ddeexec".

5 6

Logging on to the Symantec OpsCenter console

You must supply logon credentials on the OpsCenter login screen.

52

Getting started using Symantec OpsCenter About starting the OpsCenter console

To log on to the Symantec OpsCenter console

Enter a user name and password, and select a domain from the Domain drop-down list. For administrator initial logon, the user name is admin and the password is password or any custom password that you chose during the installation. Select OpsCenterUsers(vx) from the Domain drop-down list. The domains that appear in the Domain drop-down list include the OpsCenterUsers(vx) domain, domains that are migrated if you upgraded to OpsCenter from NOM or VBR, and domains of the users that are added to the OpsCenter console. After the initial log on, change the user name and password. To change existing passwords, use Settings > User Preferences > My Profile view in the OpsCenter console. See Changing your OpsCenter password on page 307.

Click Log On. Initially, a monitoring overview of the NetBackup master servers appears. When you log off from the console, OpsCenter saves your settings and preferences and uses these settings when you restart the console again. Note: The first time you log on, OpsCenter uses the default language of the Web browser. If OpsCenter does not support this language, it uses English. After initial logon, you can specify a default language or locale from Settings > User Preferences > General. If you do not set a default, OpsCenter uses the Web browser language (or English). See Setting user preferences on page 304.

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.

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.

Solution
Enter a valid user name, password, and domain. Ensure that the Symantec Product Authentication Service is started and running properly. You can start the authentication service by running net start vrtsat' on Windows and /opt/VRTSat/bin/vxatd on UNIX.

You have a user authentication error. The login screen displays the message "User authentication failed. Please enter valid user name and password. If problem persists contact your system administrator." The entered user name is not a registered OpsCenter user. The login screen displays the message "This user is not authorized to use OpsCenter. Please contact the OpsCenter Administrator for adding this user."

The user name Log on as the OpsCenter admin user and and domain add the user to the list of OpsCenter users. are valid, but the user was not added to the list of users for OpsCenter.

You cannot connect to the The OpsCenter OpsCenter server. The login server is not screen displays the message running. "Error occurred while connecting to the OpsCenter Server. Please ensure that the server is running."

Start the Symantec OpsCenter Server Service and verify that it is running properly. See 'Controlling OpsCenter services and processes' section in the Administration chapter of the Symantec OpsCenter Administrator's Guide. Check your network configuration. Verify that the hosts file has the correct IP address to host name mapping. The hosts file is located in C:\WINDOWS\system32\drivers\etc directory on Windows.

Either the user name or password or both have not been entered. The login screen displays the message "Please enter valid user name and password. "

Username and/or password has not been specified.

Enter a valid user name and password.

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. You can connecting to the Symantec start the authentication service by running Product Authentication net start vrtsat on Windows or Service (AT). Please ensure /opt/VRTSat/bin/vxatd on UNIX. that the AT service is running."

Logging out of the OpsCenter console

When you log out from the console, OpsCenter saves most of the settings and changes you make in an OpsCenter session. To log out from Symantec OpsCenter

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

Configuring the OpsCenter session timeout interval

When left at its default value, users are automatically logged out of the OpsCenter console when a session is left inactive for 30 minutes. However, the session timeout interval can be reconfigured. To configure the session timeout interval

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

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

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

Getting started using Symantec OpsCenter About starting the OpsCenter console

55

Change the session timeout parameter value to the desired length by changing the number encapsulated by the XML tags for session-timeout (in the example above, change 30 to the desired value). This value is set in minutes.

Stop the OpsCenter services. Enter the following command:

Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

Restart the OpsCenter services. Enter the following command:

Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start /opt/SYMCOpsCenterServer/bin/opsadmin.sh start

About possible OpsCenter console issues

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

Issues when you use OpsCenter console Solution

Log on again. After successful logon, you then return to the OpsCenter view that you last visited. You can also configure the session timeout interval. See Configuring the OpsCenter session timeout interval on page 54.

Cause
After 30 minutes of inactivity, the OpsCenter user automatically logs out of the console. Any attempt to use OpsCenter, displays the OpsCenter login screen.

An internal error occurs in This error results from an internal issue the OpsCenter console. An in the OpsCenter console application. exception error message appears in the OpsCenter console. You receive the message "An unknown error has occurred. Click here to log on and retry. "

Click the link in the message and try to login again.

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. You must enable it to use OpsCenter.

You receive the message Active scripting is disabled in the Web "Active scripting is required browser. to use this application. Enable active scripting in the browser."

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, type about:config and press Enter. You may see a warning message stating that this action may void your warranty. Click I'll be careful, I promise!. In the about:config page, search for the preference dom.max_script_run_time, and double-click it. At the Enter integer value prompt, type 0.

An unresponsive script error Various causes. is displayed on Mozilla Firefox

Note: Either 0 or any negative value

imply infinite time.

Press OK.

The following URLs contain more information: http://support.mozilla.com /en-US/kb/Warning+Unresponsive+script http://kb.mozillazine.org /Dom.max_script_run_time If you set scripts to run for longer times, you may no longer receive the prompt. If you still receive the prompt (or if you want to see it again), set the preference back to the default value. In the Location bar, type about:config and press Enter. You may see a warning message stating that this action may void your warranty.

Click I'll be careful, I promise!. In the about:config page, search for the preference dom.max_script_run_time. Right-click and choose Reset.

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. You can view the console by using a Web browser. When you log on initially, the Monitor > Overview view appears. The following is an example view that shows the OpsCenter console components. When you change the settings and preferences they are saved and if you log out and log on again these settings are used. Figure 1-2 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, such as Logout and Help.

Topics covered in this section Description

See About using the links on the title bar on page 59.

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.

Overview about the tabs and subtabs available in the console. Control the frequency that the OpsCenter console refreshes to reflect changes in your backup environment. Overview about the Task pane. Overview about the View pane. Overview about quick links in the task panes.

See About refreshing the OpsCenter console on page 61.

See Using the Task pane on page 61. See About the View pane on page 61. See Using the quick links in the Task pane on page 66.

Use the pane that displays a quick visual summary of See Using the Alert Summary pane on page 66. any current alerts. Use the main data display pane that OpsCenter uses. Use the status bar at the bottom of the OpsCenter console. Use the visual keys that OpsCenter uses to help you understand displayed information. Use tables, select rows, and use filters. See Using the content pane on page 67. See About the OpsCenter status bar on page 69.

See About status icons and colors in the console on page 70. See About using tables on page 71.

About using the links on the title bar

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

Medium

Large

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, click About. To access Symantec OpsCenter help, click Help. Context-sensitive help for all views, wizards, and dialog boxes is available. More information about online Help is available. See About OpsCenter documentation on page 77. To disconnect from the OpsCenter server to end your session, click Logout. See Logging out of the OpsCenter console on page 54.

About using tabs and subtabs

Table 1-6 describes the main tabs that provide access to the major areas of the OpsCenter console. Table 1-6 Tab
Monitor

Tabs and subtabs in the OpsCenter console Description

From this tab, you can monitor the status of NetBackup jobs, services, policies, media, devices, and hosts. You can also display and respond to any OpsCenter alerts. From this tab, you can manage alert policies, NetBackup job policies, storage units, and devices. You can also restore data. From this tab, you can view standard OpsCenter reports, create and run custom reports, and schedule reports.

Manage

Reports

Note: You can use custom report functionality only with a licensed
OpsCenter version (OpsCenter Analytics). Settings From this tab, you can customize the OpsCenter server, add OpsCenter users, define user preferences, add master servers, add and configure views, set up email and SNMP recipients, view chargeback settings, and so on.

Under each main tab is a series of subtabs. The contents of these subtabs vary depending on the current view and represent the views accessible from each main tab. For example, the Monitor tab includes subtabs such as Overview, Jobs, Services, and Policies. Your selection on the View pane determines what data that is shown in OpsCenter views. More information about the View pane is available.

Getting started using Symantec OpsCenter About OpsCenter console components

61

See About the View pane on page 61.

About refreshing the OpsCenter console

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

Using the Task pane

In many views in the console, a Task pane is available. The Task pane is located on the left side of the console and contains the View pane, the Symantec ThreatCon pane, and Quick Links at the bottom. To change the Task pane

1 2 3

To enlarge the Task pane, click the Collapse Task Panel icon between the Task pane and the Content pane. To show all panes after you enlarged the Task pane, click the Collapse Task Panel icon again. To resize the Task pane, drag the line separating the Task pane and the Content pane. The minimize or maximize settings are applicable only for the current session. 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. This pane lets you select the views to control the scope of your console views. ALL MASTER SERVERS is the default view in the View pane. Using OpsCenter views, you can view NetBackup information for your entire management domain (with the ALL MASTER SERVERS view), a specific view type, or an individual server. You can create views from Settings > Views or by using the Java View Builder. For example, you can create a view named Geography to display details about master servers in a particular region, such as Europe. You can also create client or policy views.

62

Getting started using Symantec OpsCenter About OpsCenter console components

More information about how to create views from Settings > Views is available. See About OpsCenter views on page 409. See the online Java View Builder Help for more informaiton about creating views using Java View Builder. The View pane has the following features:

It is available in any OpsCenter view where you can change the view. It uses unique icons and colors to convey operational states. For example, an icon with a red-dashed-circle represents a managed server that is Not Connected. Similarly, a disabled master server is shown as a gray-colored icon. See About status icons and colors in the console on page 70. It lets you access and change the views that you monitor or manage. As you navigate within the OpsCenter console, your view selection applies for any subsequent screens until you select a different view. The View pane is one method that you can use to determine the scope of information that you view. See About making multiple or single-click selections in the View pane on page 63. See About selecting views from the View pane when the multiple selection option is checked on page 64.

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

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. The Allow Multiple Selection In View Pane option governs how you can make selections in the View pane. To see the Allow Multiple Selection In View pane option, click Settings > User Preferences > General in the OpsCenter console. You can make selections in the View pane in the following ways, 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, you can select multiple nodes or view objects from the View pane. The multiple-selection option is checked by default. You also see a check box next to each master server or node in the View pane. To view data for multiple master servers and nodes, check the corresponding check boxes and click Apply Selection. Uncheck Allow Multiple Selection In View Pane option With the multiple-selection option unchecked, you can only select a single node or view object from the View pane. (The NetBackup Operations Manager (NOM) used this method.) Each node or a view object is a link. You can click a node or a view object to view data for the respective node or view object. For example, you can click a master server in the View pane to view data for the specific master server.

Note: When you uncheck the multiple-selection option, a

Group Component Summary table is displayed when you click Monitor > Jobs > Summary View. See About the Group Component Summary table on page 445.

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

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. Figure 1-5 Making single-click selections in the View pane

You can select only one master server. Each master server is a link

About selecting views from the View pane when the multiple selection option is checked
From the View pane, you can select a view and a node that contains a group of master servers and also specific objects. For example, you can select the default view, ALL MASTER SERVERS. When you select a view such asALL MASTER SERVERS or a node that contains a group of master servers, all the master servers

Getting started using Symantec OpsCenter About OpsCenter console components

65

that are currently in the view or node are automatically selected. The master servers that you may add later to this view or node are also automatically selected. You also have the option to select only specific objects of a particular view or node. For example, you may select only specific master servers under the default view ALL MASTER SERVERS. To select a specific master server, first deselect the view or node that contains the master server and then select the master server. You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. Consider a scenario in which server A and server B exist in a particular view, such as ALL MASTER SERVERS. Suppose that you select the ALL MASTER SERVERS view and then specifically deselect server B. Then, you select a node that also contains server B. In this case, even though server B is part of the selected view or node, it is not considered. It is not considered because you specifically excluded server B from the ALL MASTER SERVER view. When you specifically deselect a master server from a view, and that master server is also part of another selected view, the exclusion (the deselection) has a higher priority. For this reason, it is recommended that you do not repeat a master server across groups.

About the Symantec ThreatCon pane

The Symantec ThreatCon pane shows the current ThreatCon level in the OpsCenter console. This level is the same as the ThreatCon level which is shown on the following Web site: http://www.symantec.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. 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.

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. You can configure the polling interval. The Symantec ThreatCon feature is enabled by default, but you can disable it (or re-enable it). See Configuring Symantec ThreatCon feature in OpsCenter on page 312.

Using the quick links in the Task pane

In many views in the console, a Task pane is available. At the bottom of the Task pane, there are quick links to the most common tasks in OpsCenter. Table 1-7 shows the quick links available in OpsCenter and where they take you when you click them. 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

Click the minimize icon (the down arrow) located on top of the quick links. Only the icons for quick link tasks are visible when the quick links are minimized. Click the maximize icon (the up arrow) again to view the quick links. Note: The quick links are shown by default in a maximized state. The minimize or maximize settings are applicable only for the current session.

Using the Alert Summary pane

The Alert Summary pane provides a visual summary of the critical, major, warning, and informational alerts for the NetBackup master servers to which you are connected. This pane is available in the Monitor view and Manage view of

Getting started using Symantec OpsCenter About OpsCenter console components

67

the OpsCenter console. The number of alerts that you see is based on your View pane selection. To view outstanding alerts quickly

Click any of the four available alert counts. A filtered detail view for that alert category appears. This view is a shortcut to the Monitor > Alerts view.

Using the content pane

When you initially log on to Symantec OpsCenter, the content pane displays a summary of information for all master servers in the OpsCenter console. Initially, a monitoring overview appears (Monitor > Overview). Information in the content pane varies and is context sensitive to current selections in the View pane, the tabs and subtabs, and the time frame. To change the Content pane size

1 2 3

To enlarge the Content pane, click the Collapse Task Panel icon between the Task pane and the Content pane. To show all panes after you enlarged the Content pane, click the Collapse Task Panel icon again. To resize the Content pane, drag the line separating the Task pane and the Content pane. The minimize or maximize settings are applicable only for the current session. Note: You cannot resize the Content pane from Monitor > Overview page.

Using the List, Summary, Hierarchical, and Details views

Most of the OpsCenter Monitor views and Manage views present information in three main viewing modes: List View, Summary View, and Hierarchical View. You can view information about your NetBackup environment in any of the available views. Use the drop-down list on the top-right corner of the OpsCenter console to switch these views. Note: Not all viewing modes are available for all Monitor views and Manage views. If the viewing modes are available, the drop-down list is displayed.

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. The List View and Hierarchical View present information in tabular formats. For example, 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, clickList View To view a summary of all NetBackup jobs for a master server in the form of pie charts, click Summary View. To view details about all NetBackup jobs and relationships between jobs for a master server in a tabular format, click Hierarchical View.

A Details view is available on some of the Monitor views, Manage views, and Settings views. The following figure shows the Details view.

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 presents detailed information about an entity and shows contents of all the tabular columns for the specific entity. The view presents details on the displayed information and on the available information for the specific entity. For example, the Details view on the Monitor > Jobs page (List View) shows detailed information about a specific job ID. Information in the Details view can be viewed from tabs available in the view. To change the Details view

1 2

To minimize the Details view, click the icon (the down arrow) between the Details view and the upper part of the Content pane. To maximize the Details view, click the icon (the up arrow) between the Details view and the upper part of the Content pane. The minimize or maximize settings are applicable only for the current session.

To resize the Details view, drag the line separating the upper part of the Content pane and Details view.

About the OpsCenter status bar

The status bar at the bottom of the OpsCenter console shows a Page generated value. The Page generated value shows the date and time on the OpsCenter server

70

Getting started using Symantec OpsCenter About OpsCenter console components

to which you logged on. The date and time are adjusted to match your time zone. This value updates when the view changes or refreshes. More information on how to specify your time zone is available. See Setting user preferences on page 304.

About status icons and colors in the console

To help you understand the information it presents, OpsCenter uses status icons and color. Tool tips provide brief descriptions of the tool and the status icons that appear in OpsCenter views. A tool tip appears when you place the mouse over an icon. When OpsCenter detects a condition for a managed NetBackup server, job, drive, or drive path, you see a status icon. The icons use colors to represent critical, warning, or informational conditions. Together, the icons and colors let you quickly determine the status of a particular area in your NetBackup environment. For example, the Monitor > Jobs view contains green icons for running jobs. Unique icons appear in the drive details view for shared drives available with the NetBackup Shared Storage option (SSO). These icons represent the shared drives that are operating on all servers that share the drive. 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). Table 1-8 lists the icons that are used for managed NetBackup master servers in the View pane. Table 1-8 Icon Icons used for managed master servers Description
A normal, blue-gray server icon means that the managed server is connected. A server icon that has a red circle with a line drawn through it means that the connection to the managed server is lost. OpsCenter tries to connect again after 10 minutes. A managed server icon with a line through it denotes that the server is partially connected. For a partially connected master server, OpsCenter tries to reconnect to NBSL every 10 minutes in order to collect data for the data types that have a Failed collection status. A gray server icon means that data collection for the managed server was disabled by the user.

OpsCenter uses the following colors in the interface:

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. Investigate critical conditions immediately. Green indicates a normal condition, result, or operation. Blue-gray generally indicate conditions such as enabled or assigned, while gray indicates conditioned such as disabled or unassigned.

About using tables

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

Sample screen with task options for tables

Table Settings icon

Table page controls

Customizing tables for your needs

You can customize the tables in the following manner. You can perform the following operations to a table:

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.

Rearrange the order of the columns for your See Moving a column on page 72. 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. Sort columns in ascending or descending order Change the widths of columns See Sorting the contents of a table column on page 73. See Changing the width of a column on page 73. See Accessing multiple pages of data in tables on page 73. See Selecting rows in tables on page 74.

Configure pagination

Select rows in tables

The table refreshes after the operation and shows the changes you made. For these operations, OpsCenter saves and reloads your customized settings when you log on to the OpsCenter server again. Each user can have different customized table settings.

Specifying which columns appear in a table

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

1 2

Click the Change Table Settings icon at the top-right corner of the table. Initially, some OpsCenter tables do not show all available columns. To view any of these columns, you may first have to remove one or more columns from the table and then add the missing columns. To remove columns you do not want to appear, select the column in Selected Columns and click Remove. To add any columns that currently do not appear, select the column in the Available Columns list and click Add. Added columns appear as the last column in the table.

Moving a column
Use the following procedure to move columns in a table.

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. Select the name of the column in Selected Columns. Click Move Up to move the column to the left in the table. Click Move Down to move the column to the right in the table.

Choosing the number of table rows that appear per page

Use the following procedure to choose the number of table rows that appear per page. 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. Select a number from the Rows Per Page drop-down list . Select Apply To All Tables if you want the Rows Per Page setting to apply to all tables in OpsCenter. The setting applies to reports also.

Sorting the contents of a table column

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

In a table, click the column name. The column sorts in ascending order by default. To sort in descending order, click the column name again.

Changing the width of a column

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

1 2

Select the edge of the column heading and hold down the left mouse button. Drag the edge of the column heading to the right or left.

Accessing multiple pages of data in tables

Much of the monitoring information appears in a table format. OpsCenter tables display 10 rows at one time by default. To change the number of rows that are displayed, use the Change Table Settings icon. When you have more data to display than can fit in a table, the table contains multiple pages. Use the table page controls that are located below the table to help you navigate the pages.

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, use the table page controls. To go to a specific page

Click the page number.

To go to the previous or the next page

Click the left arrow or the right arrow.

To go to the first or the last page

Click the double left arrow or the double right arrow.

Selecting rows in tables

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

Click the check box for that row. Click the check box again to deselect the selected row.

To select all rows on the current page of the table

Click the check box in the header row of the table. Click the check box again to deselect all selected rows.

Using filters to customize your views

Many tables in OpsCenter let you display a subset of the information available by creating and using custom filters, or by using the predefined (ready-to-use) filters. A filter screens information that is based on a set of conditions that you define. Once you create a filter, you can save it, edit it, or remove it. In the views that allow filtering, filtering icons appear above the table. The following procedures describe how you can create, apply, edit, or remove a filter. To create a custom filter

1 2

Select the Create Filter icon. Type a name for the filter in the Name field.

Getting started using Symantec OpsCenter About OpsCenter console components

75

For Column, select the column name that you want to filter on from the drop-down list. For Operator, select an operator. Use != if you do not want to match a specific value. For Value, enter or select a value. If you select Start Time or End Time for Column, a calendar icon appears for Value. Click the calendar icon to choose a date and time and then click OK.

From the drop-down list, select And or Or to build the filter query. For Link, click Add to add another clause to the query. If the clause is not what you want, click Remove to remove the clause from the query.

To continue building the filter, select another column. Repeat 3 and 4.

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

To apply a filter

From the drop-down list, select a custom filter or a OpsCenter built-in filter. OpsCenter filters the table according to the criteria you specify. The view remains in effect until you change it by selecting another filter.

To edit a custom filter

From the drop-down list, select a custom filter. Note: You cannot modify the predefined OpsCenter filters. You can only modify custom filters.

2 3

Click the Edit filter icon. See To create a custom filter on page 74. This lists the instructions for using the dialog to edit a filter. Make your changes and click OK.

76

Getting started using Symantec OpsCenter About quickly performing common tasks in OpsCenter

To remove a custom filter

From the drop-down list, select a custom filter. Note: You cannot delete the predefined filters.

2 3

Click the Delete filter icon. Click OK to remove the filter.

About quickly performing common tasks in OpsCenter

Table 1-9 lists common tasks and corresponding links to the documentation. 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. See About managing Symantec OpsCenter users on page 321. See Setting user preferences on page 304. See Configuring SMTP server settings for OpsCenter on page 311. See About managing recipients in OpsCenter on page 330. See Creating OpsCenter views on page 415.

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. View and respond to OpsCenter alerts See Managing an alert policy on page 517. View the details for a NetBackup job See About monitoring NetBackup jobs on page 433. See About monitoring NetBackup policies on page 453. See Activating or deactivating a job policy on page 459.

View NetBackup job policies

Control NetBackup job policies

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. See Monitor > Services view on page 451.

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. licensed (Symantec OpsCenter Analytics version of the product. Schedule when you want a report to run See About managing report schedules in OpsCenter on page 604.

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. You can use the bookmark to return to the same view when you log onto the console again.

About OpsCenter documentation

The Symantec OpsCenter Administrator's Guide (NetBackup_AdminGuide_OpsCenter.pdf) provides information on how to use OpsCenter. It includes information about how to monitor and manage NetBackup, to collect data from Symantec products as well as third-party products, to generate alerts, and to create various reports. It also provides details on the new enhancements in OpsCenter 7.1 and also how you can install OpsCenter 7.1. Note: For the latest support information about supported products and operating systems, see the Symantec NetBackup Hardware and Software Compatibility List. The list is regularly updated on the Symantec Support Web site: http://www.symantec.com/business/support You can find more information about OpsCenter 7.1 in Symantec NetBackup 7.1 Release Notes. Always refer to the OpsCenter sections of the NetBackup 7.1 Release Notes for any last-minute changes to the information that is presented in this

78

Getting started using Symantec OpsCenter About OpsCenter documentation

document. The Release Notes also include any restrictions or limits for OpsCenter 7.1. You can access the Release Notes from the following URL: http://www.symantec.com/docs/DOC3412 In addition to this Symantec OpsCenter Administrator's Guide PDF, OpsCenter 7.1 is also shipped with the following online Help documents:
OpsCenter Context-sensitive This Help provides information about the OpsCenter user Help interface. It provides context-sensitive help pages for all screens. Java View Builder Context-sensitive Help This Help provides information about all Java View Builder procedures and dialog boxes. To access the Help, click Help in a dialog box in the Java View Builder console.

NetBackup Status Codes Help This Help provides descriptions of NetBackup status codes and possible actions to take when a code appears. To access the Help, click Monitor > Jobs. Click a status code link in the jobs table to view its details. Table Settings Help This Help provides information on how to change the settings of a table in the OpsCenter console. To access the Help, click Help on the Table Settings pop-up dialog box.

Chapter

Installing Symantec OpsCenter 7.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.

About the software components that OpsCenter uses

Along with OpsCenter-specific components, OpsCenter uses some Symantec components that are shared.

About components shared with other Symantec applications

OpsCenter used the following components that are also shared with other Symantec applications:

80

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

Symantec Private Branch Exchange (PBX) PBX lets applications share a common TCP/IP port, which reduces the required number of open ports in firewalls. PBX also integrates with the Symantec Product Authentication Service to allow for authenticated connections and non-authenticated connections. Because PBX is an independent component, its port number can be changed using PBX configuration files. Note: If you change the PBX port number on the OpsCenter server, OpsCenter may fail. Symantec Product Authentication Service (AT) The AT service is primarily used for user logon authentication. AT is required for secure communication among the OpsCenter Agent, Server, View Builder, and user interface. It is also used for secure communication between NetBackup master servers and the OpsCenter Server. The OpsCenter Server needs to be a legitimate server that can communicate with NetBackup; it must be on the NetBackup server list. OpsCenter does not require that you install the Symantec Product Authorization Service. The NetBackup Authentication Service (NBAC) does not need to be configured on your managed NetBackup master servers. See the NetBackup Security and Encryption Guide for information about authentication services and about NBAC. JRE (Java Runtime Environment ) The Symantec OpsCenter Web server and the OpsCenter application require this component.

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. OpsCenter uses VxUL to configure and view logs. See the NetBackup Troubleshooting Guide for more information about VxUL logs. Sybase database

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

81

OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation that is separate from the NetBackup database. More information about the Sybase component is available at the following location: http://www.sybase.com/support/manuals

About the OpsCenter licensing model

OpsCenter requires no license. To enable additional functionality you can add a license key to enable Symantec OpsCenter Analytics. The licensed version of OpsCenter is called Symantec OpsCenter Analytics. The unlicensed version of OpsCenter is called Symantec OpsCenter. The product name is visible from the title bar and logon page of the OpsCenter console. The charges for Symantec OpsCenter licenses are based on how many entities you require reports on, as follows:

For backup environments, the charges are based on the number of backup clients. For Symantec Enterprise Vault environments, the charges are based on the number of mailboxes.

Note: If you want to enable custom reporting on Enterprise Vault data, you must add the appropriate license key. For example, assume that your NetBackup environment contains 100 clients to back up. You also run Enterprise Vault and have 500 mailboxes. You must purchase a license that allows reporting for 100 backup clients and 500 mailboxes. The Symantec Enterprise Vault license is option called Archive Mailbox is added. If you install the Archive Mailbox option, it is visible in the OpsCenter console on the Settings > Configuration > License page. You compare the configured number of mailboxes or backup clients with the license limit. Examine the Value column and the Usage column on the Settings > Configuration > License page. If you have a license for 1000 mailboxes, it is added as 'Archive Mailbox' as shown in the figure.

82

Installing Symantec OpsCenter 7.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. These entries show that the actual usage of Archive mailbox license option is 0 while the licensed value is 1000.

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. The demo key lets you try the product before you purchase it. A permanent key does not have an expiry date.

Permanent key

You can access the licensed features with both demo keys and permanent keys. With Symantec OpsCenter Analytics, you can perform advanced reporting, create custom reports, and collect data from third-party products such as IBM Tivoli Storage Manager and EMC Networker. See About the Symantec OpsCenter Analytics licensed features on page 83. You can also add, delete, or view license keys after installation from the OpsCenter console. See About managing licenses on page 307.

Installing Symantec OpsCenter 7.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. 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.

Symantec OpsCenter
Symantec OpsCenter is visible from the title bar and logon page of the OpsCenter console. Symantec OpsCenter lets you do operational reporting.

Symantec OpsCenter Analytics lets you perform advanced, business-level reporting. With Symantec OpsCenter Analytics, 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. More information about the licensed features is available. See About the Symantec OpsCenter Analytics licensed features on page 83. 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.

About the Symantec OpsCenter Analytics licensed features

Table 2-2 shows the list of licensed features, where they are located in the OpsCenter console, and how they appear in the unlicensed version.

84

Installing Symantec OpsCenter 7.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. 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. 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. back Reports Settings > Charge back Charge back settings are disabled. You cannot create or edit data collectors for third-party products.

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, in the Select Product drop-down list, TSM and EMC Networker options are disabled. Settings > Configuration > Agent > Edit Data Collector

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

85

Table 2-2 Licensed feature

Full control over report time frame selection. You can view report data for any previous date.

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. Time frame window on the Select Parameters page.) Reports > My Reports > Create New Report (Relative and Absolute Time frame window on the Select Parameters page.) Report > Report templates (Run a report, click Edit Report and then Relative and Absolute Time frame window.) Reports > My Reports (Run a report, click Edit Report and then Relative and Absolute Time frame window.)

Reconcile Task

Monitor > Jobs. The Reconcile option The Reconcile option is disabled. under the More drop-down list is disabled. Settings > Edit View level Alias The Edit View level Alias tab is disabled. 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.

About Symantec OpsCenter DVD's

Symantec OpsCenter 7.1 is shipped with three OpsCenter DVD's. Three OpsCenter DVD's are available and are a part of the NetBackup media kit. Table 2-3 describes the contents of each DVD.

86

Installing Symantec OpsCenter 7.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.1 software is not a part of the NetBackup DVD's. You can either install an unlicensed version, a demo version, or purchase a Symantec OpsCenter Analytics license key and install the licensed version. With the demo version, you can access the Symantec OpsCenter Analytics features for 60 days (starting from the day you install the demo key). See About the OpsCenter licensing model on page 81.

About OpsCenter platform compatibility

This section provides information about OpsCenter platform compatibility. Note: Refer to the compatibility matrix that is posted on the Symantec Support Web site for the latest information on the platforms that OpsCenter supports. This document is posted at the following URL: http://www.symantec.com/docs/TECH59978

Installing Symantec OpsCenter 7.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.31 AIX 5.3 AIX 6.1

No No No No

No Yes Yes Yes

No No No No

Yes No Yes No

No No No No

No No No No

No No

Yes Yes Yes

No No No

No No No

No No No

No No No

Linux RedHat 4.0, No 5.0 Linux SUSE 10 Linux SUSE 11 ( 2.6.5-*, 2.6.9-*, 2.6.16-*, 2.6.18-*, 2.6.27-*, 2.6.32-*) where * is the kernel-smp version No

Yes

No

No

No

No

88

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

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

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

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. Important notes on operating systems:

If installing OpsCenter on AIX, ensure that the XLC runtime version is 9.0 or higher. If installing OpsCenter on AIX 6.1, ensure that you install the applicable patch for AIX from the IBM site: http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105097 OpsCenter Server is not supported on non-global Solaris zones. OpsCenter Server and Agent are supported in a VMware virtual machine guest operating system environment. 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. OpsCenter deployment limitations:

You must install Server, Agent, and View Builder of the same versions. For example, Server 7.1 is only compatible with Agent 7.1 and View Builder 7.1. Only the OpsCenter Server can be installed in a clustered mode on UNIX and Windows, with Veritas Cluster Server (VCS). The OpsCenter Agent and View Builder are not supported on VCS. The OpsCenter installer automatically sets the maximum heap size to 1024 MB. Your system may require a lesser max heap size to properly run all applications. See Adjusting the heap size for OpsCenter components on page 221.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

89

Installing OpsCenter components in a location that is mounted from a remote host is not supported on UNIX. If 8.3 file name creation is disabled on a Windows host, it is recommended that you enable it and restart the Windows host before installing or upgrading to OpsCenter components. If you install or upgrade to OpsCenter components on a Windows host where 8.3 file name creation is disabled, then you must do the following:

Install OpsCenter components on a customized (non-default) location like D:\Favorites. The default installation location of OpsCenter components is C:\Program Files\Symantec. Ensure that the customized location that you provide does not contain spaces or special characters like %, ).

Ensure that the OpsCenter Server hostname does not contain any underscores like opshost. 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. A backup product host or an archive product host means a supported product host that is connected to OpsCenter. Examples of a backup product host or an archive product host are PureDisk host, Backup Exec host, NetBackup master server, Enterprise Vault host etc. If the OpsCenter server and the product host are in the same time zone, both the OpsCenter server and the product host must show the same time. For example, if the OpsCenter server and the product host are in the CST time zone, but show different times, such as 8:00 P.M. and 9:00 P.M., OpsCenter may not display accurate data in the reports or in the Monitor tab and Manage tab. If the OpsCenter server and product host are in different time zones, ensure that both time zones convert to the same GMT time. For example, if the OpsCenter server shows 8:00 P.M. C.S.T and the managed host shows and 6:00 P.M. P.S.T, they must translate to the same GMT time (such as GMT -6).

About OpsCenter compatible backup and archiving products

This section lists the backup and archiving products that OpsCenter supports. Note that with the licensed version of OpsCenter, you can perform advanced reporting from the data that is collected from all of these products. With the unlicensed version, you cannot collect data from third-party products like IBM TSM and EMC Networker. Table 2-5 lists the backup and archiving products that OpsCenter supports.

90

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

Table 2-5

Backup and archiving products supported by Symantec OpsCenter 7.1 Versions

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

Backup or Archiving product

Symantec NetBackup

Support level
All supported NetBackup platforms (except 7.1) by remote agent

Note: NBU 7.1 does not require any

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

Symantec NetBackup PureDisk

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

PureDisk supported platform (PDOS) by the OpsCenter integrated Agent. You do not need a separate Agent to collect data from PureDisk. You can use the inbuilt Agent of the OpsCenter Server for data collection. To create or configure the data collector, select the Agent that is installed as Integrated Agent.

Symantec Backup Exec

10d, 11d, 12.0, 12.5, 2010, All supported Symantec Backup 2010 R2 Exec platforms by remote agent.

Note: OpsCenter does not Native agent on backup servers on

support Symantec Backup Windows 2003 (SP2 & R2), 2008 Exec running on NetWare. (SP2 & R2) Symantec Enterprise Vault 7.5, 8.0 All supported Symantec Enterprise Vault platforms by remote agent Native agent on Microsoft SQL Server 2005 or 2008 (where Enterprise Vault database resides) on Windows 2003 (SP2 & R2), 2008 (SP2 & R2). EMC NetWorker 7.3 Native agent on backup servers on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

91

Table 2-5

Backup and archiving products supported by Symantec OpsCenter 7.1 (continued) Versions
5.3, 5.4, 5.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), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.

About managed NetBackup master server considerations

Consider the following recommendations and requirements for your managed NetBackup master servers. 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. An example is the master server on which the OpsCenter server software is installed. To monitor more than one master server, Symantec recommends that you install the OpsCenter server software on a separate standalone server. More information on sizing guidelines is available. See About OpsCenter sizing guidelines on page 94.. OpsCenter does not collect data from the managed servers that are configured within a network address translation (NAT) network. The OpsCenter server should be configured as a fixed host with a static IP address. Symantec recommends that any NetBackup master server is monitored by only one OpsCenter server. The OpsCenter Server must be at an equal or higher version than the NetBackup master server version that it monitors. For example, OpsCenter 7.1 can monitor all NetBackup master server versions between 6.0 MP7 and 7.1. If you plan to upgrade both NetBackup master server and the OpsCenter Server, it is recommended that you upgrade OpsCenter Server before upgrading the NetBackup master server. By upgrading OpsCenter Server before the NetBackup

92

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

master server, OpsCenter can start collecting data from the master server once it is added.

OpsCenter can be used to monitor a NetBackup cluster. See NetBackup High Availability Administrator's Guide for more details on setting up a NetBackup cluster environment.

More information about adding managed NetBackup servers in OpsCenter is available. See Adding a master server in the OpsCenter console on page 385.

About using NBSL to collect data from NetBackup master servers

A NetBackup master server with version 7.1 does not require any Agent or data collector for data collection. The OpsCenter server uses the NetBackup Service Lay (NBSL) to collect the data from a NetBackup 7.1 master server. For a 6.5.x master server, an Agent must be installed if you want to collect image data, error log data, scheduled jobs data, and breakup jobs data. Similarly, for a 6.0.x master server, an Agent must be installed if you want to collect image data or error log data. If you do not want to collect such data, you do not need to install an Agent. OpsCenter uses NBSL to collect all the other data automatically from the master server. For a 7.0.x master server, an Agent must be installed if you want to collect breakup jobs data. If you do not want to collect the breakup jobs data, you do not need to install an Agent. OpsCenter uses NBSL to collect all the other data automatically from the master server. Beginning with NetBackup version 6.0, NBSL components are included as a part of NetBackup on master and media servers. OpsCenter requires NBSL for all NetBackup monitoring, managing, and control functions. OpsCenter is affected if NBSL stops running on a managed NetBackup server. If NBSL stops, OpsCenter may not capture any changes that were made to the NetBackup configuration. When NBSL restarts, OpsCenter correctly recaptures the latest state.

Design your OpsCenter Server

Before setting up an OpsCenter Server, review the recommendations and requirements that are listed in the earlier sections. See About managed NetBackup master server considerations on page 91.

Installing Symantec OpsCenter 7.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. 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, 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. The database is installed as part of the OpsCenter server installation. Note the following:

After you configure OpsCenter, OpsCenter disk space depends on the volume of data initially loaded on the OpsCenter server from the managed NetBackup servers. The initial data load on the OpsCenter server is in turn dependent on the following data present in the managed master servers:

Number of policy data records Number of job data records Number of media data records

The rate of OpsCenter database growth depends on the quantity of managed data. This data can be policy data, job data, or media data.

Information is available on how to adjust database values for better OpsCenter performance. See Tuning OpsCenter for more performance on page 213.

94

Installing Symantec OpsCenter 7.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. 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, 0-20 8 GB RAM 4 Processors, 20-40 8 GB RAM 8 Logical 40-60 Processors, 8 GB RAM 16 Logical Processors, 16 GB RAM 60-100

0 - 10,000

0 2000

0 1000

0 20,000

10,000 40,000 40,000 60,000

2000 4000

1000 10,000 20,000 40,000 10,000 50,000 40,000 60,000

4000 6000

60,000 1,00,000

6000 10,000 50,000 1,00,000

60,000 1,50,000

Note: Some of the data in this table has been interpolated. Symantec recommends that the memory of the system where you install OpsCenter Server is 8 GB or more. 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. If NetBackup and the OpsCenter Server are installed on the same system, Symantec recommends that you run no more than 5000 NetBackup jobs daily. If the number of NetBackup jobs that run daily on the master server is more than 5000, Symantec recommends that you install OpsCenter server software on a separate standalone system . Information is available on how you can tune OpsCenter for better performance. See Tuning OpsCenter for more performance on page 213.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

95

About supported upgrade paths

OpsCenter supports direct upgrades from the following versions:

OpsCenter 7.0 to OpsCenter 7.1 OpsCenter 7.0.1 to OpsCenter 7.1 VBR 6.6.1 to OpsCenter 7.1 VBR 6.6.2 to OpsCenter 7.1 NOM 6.5.4 to OpsCenter 7.1 NOM 6.5.6 to OpsCenter 7.1

Note: If you have an earlier version of NOM or VBR, first upgrade to a supported version. See the product documentation for details on how to upgrade.

About OpsCenter Agent deployment

This topic describes the deployment scenarios for the OpsCenter Agent. It helps you decide how to deploy the Agent in your environment. Note: You must install OpsCenter Server, Agent, and View Builder of the same version. For example, Server 7.1 is only compatible with Agent 7.1 and View Builder 7.1. You can deploy the OpsCenter Agent on the OpsCenter Server host or the product host (for example, a NetBackup master server whose version is earlier than 7.1, a Backup Exec host, or an Enterprise Vault host). You can also deploy the OpsCenter Agent on a separate host, which is referred to as a Remote Agent. The deployment that you choose depends on the product that you want to collect data from and its operating system.

96

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

Note: A NetBackup version 7.1 master server not require any Agent for data collection. The OpsCenter Server uses NBSL to collect the data automatically from the NetBackup master server. For a 6.0.x or a 6.5.x master server that runs an earlier version than 7.0, an Agent must be installed if you want to collect image data, error log data, scheduled jobs data, and breakup jobs data. If you do not want to collect such data, you do not need to install an Agent. OpsCenter uses NBSL to collect all the other data automatically from the master server. Note that for a 6.0 MP7 master server, you cannot collect scheduled jobs and breakup jobs data. Hence for a 6.0 MP7 master server, an Agent must be installed if you want to collect data image data or error log data. For a 7.0.x master server, an Agent must be installed if you want to collect breakup jobs data. If you do not want to collect the breakup jobs data, you do not need to install an Agent. OpsCenter uses NBSL to collect all the other data automatically from the master server.

Note: You do not require an OpsCenter Agent to collect data from PureDisk. If you installed the VBR Agent only to collect PureDisk data, you must manually uninstall it. See About OpsCenter compatible backup and archiving products on page 89. A single Agent can have multiple data collectors configured that collect data from different product hosts. Note: For NetBackup servers and EMC Networker hosts, you need separate OpsCenter Agents to collect data from servers with different versions. See About data collection in OpsCenter on page 347. You can install only one Agent on a single host; it can have multiple data collectors configured. (Data collectors were formerly called Agent Modules.) See Installing Symantec OpsCenter on Windows and UNIX on page 106.

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.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

97

NetBackup

You need separate Agents to collect data from different versions of NetBackup master servers. 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 . You can configure an Agent to collect the following data from master server versions below 7.1: 6.0.x Install an Agent if you want to collect data for image or error logs. 6.5.x Install an Agent if you want to collect data for image, error log, scheduled jobs, or breakup jobs. 7.0.x Install an Agent if you want to collect data for breakup jobs.

Note: A NetBackup master server with version 7.1 does not

require any Agent for data collection. PureDisk PureDisk data collection does not require a separate Agent. You can use the Integrated Agent of the OpsCenter Server for data collection. To create or configure the data collector, select the Agent that is installed as the Integrated Agent.

Note: You do not require an OpsCenterAgent to collect data

from PureDisk. If you installed the VBR Agent only to collect PureDisk data, manually uninstall the VBR Agent. See Configuring PureDisk data collector on page 391. Backup Exec You can use the same Agent to collect data from Backup Exec servers with different versions.

Note: To collect data from a Backup Exec server host, you

need to install the Agent on a compatible Windows host. IBM TSM You can use the same OpsCenter Agent to collect data from TSM servers with different versions. You need different OpsCenter Agents for EMC Networker servers with different versions. The OpsCenter Agent needs to be installed on the EMC Networker server host.

EMC Networker

98

Installing Symantec OpsCenter 7.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.

Note: To collect Enterprise Vault archive data, you must

install the OpsCenter Agent on a Windows host.

About installing the OpsCenter Agent on a product host

The OpsCenter Agent can be installed on a product 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. You must install the Agent on the EMC Networker host.

Installing the OpsCenter Agent little affect on the backup environment. The OpsCenter Agent must be compatible with the operating system of the backup application host. Installing the Agent on a remote backup application host has the following advantages:

Ease of maintenance for upgrades, because you only service one host. Minimal intrusion on backup hosts, because only one agent is installed on a backup host.

A disadvantage of installing the OpsCenter Agent on a remote backup application host is that the Agent may use significant system resources, which can affect the backup application hosts performance.

About installing the OpsCenter Agent on a host other than a product host
The OpsCenter Agent can be installed on a host different than the product host; this is sometimes called a Remote Agent. The different host may be the OpsCenter Server host or a separate host.

Installing Symantec OpsCenter 7.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). When the product host system has insufficient resources to support co-location of the OpsCenter Agent and the backup application.

In such situations, the Agent should remotely communicate with backup products. The following products support Remote Agent installation:

Symantec Enterprise Vault Symantec NetBackup Symantec NetBackup PureDisk Note: PureDisk does not support local Agent installation, because OpsCenter does not support the PureDisk operating system. The PureDisk Server and OpsCenter Agent cannot reside on the same host. Symantec Backup Exec IBM TSM

Note: To collect data from a NetBackup master server, ensure that the Remote Agent host has the NetBackup Remote Administration Console, a master server, or a media server installed. UNIX platforms do not support the Remote Administration Console. For backup products other than Symantec Backup Exec, you need to have a backup application client executable on the Agent host to collect data remotely. See About collecting data from Enterprise Vault on page 392. 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, because the backup data is gathered remotely. You need to maintain only one host for both the OpsCenter Agent and the Server, which avoids the maintenance that might otherwise be involved in upgrading the agent.

Disadvantages of installing the OpsCenter Agent on the Server host include the following:

100

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

You must install a component of the backup application on the OpsCenter Server host. For example, assume that you need separate OpsCenter Agents to collect data from different versions of NetBackup master servers. You need to install NetBackup binaries (the Remote Administration Console for Windows, the master server, or the media server) on the Agent host that match the version of the NetBackup master server. In some situations, a backup application license key is required for the component that is installed on the OpsCenter Server host.

Examples of OpsCenter Agent deployment in a NetBackup environment

In a NetBackup environment, the following OpsCenter deployment scenarios are valid:

You install the OpsCenter Server on OpsCenterHost1, install the Agent on AgentHost1, and install a NetBackup 6.5 master server is on ProdHost1. Install the NetBackup 6.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. Install the NetBackup 6.5 Remote Administration Console or the NetBackup master server on OpsCenterHost1 and configure a data collector to collect data from ProdHost1. You install the OpsCenter Server on OpsCenterHost1, and you install the NetBackup master server and the OpsCenter Agent on ProdHost1 Configure a data collector on OpsCenterHost1 to collect data from ProdHost1. You install the OpsCenter Server and Agent on OpsCenterHost1, the NetBackup 6.5 master server is installed on ProdHost1, and you install another NetBackup 6.5 master server on ProdHost2. 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. You install the OpsCenter Server on OpsCenterHost1. You install Agent A1 on AgentHost1 and install Agent A2 on AgentHost2. A NetBackup 6.0 master server exists on ProdHost1 and you install a NetBackup 6.5 master server on ProdHost2. Install a NetBackup 6.0 Remote Admin Console or 6.0 master server on AgentHost1 and configure a data collector to collect data from ProdHost1.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

101

Install a NetBackup 6.5 Remote Administration Console or 6.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. 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. Table 2-7 Item
1.

OpsCenter install and upgrade checklist for Windows

Task
Ensure that you install OpsCenter software on a compatible platform. See About OpsCenter platform compatibility on page 86.

2. 3.

Ensure that no other installation is in progress while you install OpsCenter. If 8.3 file name creation is disabled on a Windows host, it is recommended that you enable it and restart the Windows host before installing or upgrading to OpsCenter components. If you install or upgrade to OpsCenter components on a Windows host where 8.3 name creation is disabled, then you must do the following:

Install OpsCenter components on a customized (non-default) location like D:\Favorites. The default installation location of OpsCenter components is C:\Program Files\Symantec. The customized location that you provide should not contain spaces or special characters like ( , % etc.

4. 5.

Ensure that the antivirus software is disabled before you install OpsCenter. Ensure that your OpsCenter server is configured as a fixed host with a static IP address. Ensure that the fully qualified domain name (FQDN) of your OpsCenterServer has no more than 44 characters. For a new OpsCenter installation, ensure that the database directory has at least 20 MB of available space. Note that after you install and start using OpsCenter, the database grows in size, and requires more space. See Design your OpsCenter Server on page 92.

6.

7.

102

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

Table 2-7 Item

8.

OpsCenter install and upgrade checklist for Windows (continued)

Task
If you plan to upgrade both NetBackup master server and the OpsCenter Server, it is recommended that you upgrade OpsCenter Server before upgrading the NetBackup master server. By upgrading OpsCenter Server before the NetBackup master server, OpsCenter can start collecting data from the master server once it is added. Ensure that the necessary ports are opened before you install OpsCenter on a hardened server. See About communication and firewall considerations on page 284.

9.

10.

Ensure that the name of the folder in which you are installing OpsCenter does not contain any special characters such as %, ~, !, @, $, &, ^, or #. If a file called program exists in the C: folder of your OpsCenter Server, rename or delete the file before you install OpsCenter. If you need to monitor a single master server, install OpsCenter on the NetBackup master server or media server (recommended). Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters:

11.

12.

13

Display language Location

Check your respective OS documentation for more information on these parameters. 14. Install OpsCenter Server, Agent, and View Builder of the same versions. For example, Server 7.1 is only compatible with Agent 7.1 and View Builder 7.1. If you are upgrading from NOM to OpsCenter 7.1, ensure that you have one of the following NOM versions installed:

15.

NOM 6.5.4 NOM 6.5.6

If you are upgrading from a NOM version that is not supported, first upgrade to one of the compatible versions. See the NOM documentation for details on how to perform this upgrade.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

103

Table 2-7 Item

16.

OpsCenter install and upgrade checklist for Windows (continued)

Task
If you are upgrading from VBR to Symantec OpsCenter Analytics 7.1, ensure that you have one of the following VBR versions installed:

VBR 6.6.1 VBR 6.6.2

If you are upgrading from a VBR version not supported, first upgrade to one of the compatible versions. See the VBR documentation for details on how to perform this upgrade. 17. If you are upgrading from VBR or NOM, ensure that the OpsCenter database directory has three times as much space as your NOM database or VBR database. For example, if your NOM database or VBR database is 1 GB, the OpsCenter database directory must have at least 3 GB of available space. Note that once you install and start using OpsCenter, the database grows, and requires more space. See Design your OpsCenter Server on page 92. 18. If you are upgrading from VBR to Symantec OpsCenter Analytics 7.1 and have changed the default database passwords (dba, guest, ccsvc) or databsase port numbers for VBR, you must reset these to the default values before upgrading to OpsCenter 7.1. See About upgrading from VBR to OpsCenter Server 7.1 if you use customized database passwords or port numbers in VBR on page 154. 19. 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), run DataBackupUtility.EXE from the Server directory of the OpsCenter DVD to back up the necessary data. During the OpsCenter installation, the backed up data can be restored on the compatible OpsCenter platform. See Upgrading to OpsCenter Server on a different Windows system on page 201.

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. Table 2-8 Item
1.

OpsCenter install and upgrade checklist for UNIX

Task
Ensure that you install OpsCenter software on a supported platform. See About OpsCenter platform compatibility on page 86.

104

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

Table 2-8 Item

2. 3.

OpsCenter install and upgrade checklist for UNIX (continued)

Task
Ensure that no other installation is in progress while you install OpsCenter. Ensure that your OpsCenter Server is configured as a fixed host with a static IP address. Ensure that the OpsCenter Server does not have a symbolic link to the /opt directory. Ensure that the fully qualified domain name (FQDN) of your OpsCenter Server has no more than 44 characters. For a new OpsCenter installation, ensure that the database directory has at least 20 MB of available space. Note that once you install and start using OpsCenter, the database grows in size, and requires more space. See Design your OpsCenter Server on page 92.

4.

5.

6.

7.

Ensure that the necessary ports are opened before you install OpsCenter on a hardened server. See About communication and firewall considerations on page 284.

8.

If you need to monitor a single master server, install OpsCenter on the NetBackup master server or media server (recommended). Ensure that the name of the folder in which you are installing OpsCenter does not contain any special characters such as %, ~, !, @, $, &, ^, or #. Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters:

9.

10.

Display language Location

Check your respective OS documentation for more information on these parameters. 11. Install OpsCenter Server, Agent, and View Builder of the same versions. For example, Server 7.1 is only compatible with Agent 7.1 and View Builder 7.1. If you plan to upgrade both NetBackup master server and the OpsCenter Server, it is recommended that you upgrade OpsCenter Server before upgrading the NetBackup master server. By upgrading OpsCenter Server before the NetBackup master server, OpsCenter can start collecting data from the master server once it is added.

12.

Installing Symantec OpsCenter 7.1 Planning an OpsCenter installation

105

Table 2-8 Item

13.

OpsCenter install and upgrade checklist for UNIX (continued)

Task
If you upgrade from NOM to OpsCenter, ensure that you have one of the following NOM versions installed:

NOM 6.5.4 NOM 6.5.6

If you are upgrading from a NOM version that is not supported, first upgrade to one of the supported versions. See the NOM documentation for details on how to perform this upgrade. 14. If you upgrade from VBR to Symantec OpsCenter Analytics, ensure that you have one of the following VBR versions installed:

VBR 6.6.1 VBR 6.6.2

If you are upgrading from a VBR version that is not supported, first upgrade to one of the compatible versions. See the VBR documentation for details on how to perform this upgrade. 15. If you upgrade from VBR or NOM, ensure that the OpsCenter database directory has three times as much space as your NOM database or VBR database. For example, if your NOM database or VBR database is 1 GB, the OpsCenter database directory requires at least 3 GB of available space. Note that after you install and start using OpsCenter, the database grows, and requires more space. See Design your OpsCenter Server on page 92. 16. If you are upgrading from VBR to Symantec OpsCenter Analytics 7.1 and have changed the default database passwords (dba, guest, ccsvc) or databsase port numbers for VBR, you must reset these to the default values before upgrading to OpsCenter 7.1. See About upgrading from VBR to OpsCenter Server 7.1 if you use customized database passwords or port numbers in VBR on page 154. 17. 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), run the Backup.sh script from the Server directory of the OpsCenter DVD to back up the necessary data. During the OpsCenter installation, this backed up data can be restored on the compatible OpsCenter platform. See Upgrading to OpsCenter Server on a different UNIX system on page 206.

106

Installing Symantec OpsCenter 7.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.1 on Windows and UNIX hosts. You can also upgrade from an earlier NOM, VBR, or OpsCenter installation. See Upgrading to OpsCenter on Windows and UNIX on page 136. You can install OpsCenter 7.1 in a clustered mode. See Clustering Symantec OpsCenter on page 233. Table 2-9 provides steps to install OpsCenter components. You can use this table as a checklist while installing Symantec OpsCenter. Table 2-9 Step number Step
1 Review the hardware / software requirements for OpsCenter Server and Agent hosts, carefully. Make sure that you satisfy the operating system requirements. See About OpsCenter platform compatibility on page 86. Go through the firewall settings and port number information. See About communication and firewall considerations on page 284. Go through the Agent deployment section. See About OpsCenter Agent deployment on page 95. Review the Install/Upgrade checklists before installing OpsCenter. See Before you install or upgrade on page 101. 2 Go through the appropriate installation section. Different sections are available for fresh installation, upgrade, and clustering. See Installing Symantec OpsCenter 7.1 on Windows on page 107.

Steps to install, upgrade, and cluster Symantec OpsCenter Reference topic

See Planning an OpsCenter installation on page 79.

See Installing Symantec OpsCenter 7.1 Note: After installation, verify if OpsCenter is running on UNIX on page 111. properly. See Upgrading to OpsCenter on Windows and UNIX on page 136. See Clustering Symantec OpsCenter on page 233.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

107

Installing Symantec OpsCenter 7.1 on Windows

Use the Installation Wizard to install OpsCenter on a Windows host. The three OpsCenter DVD's contain OpsCenter 7.1 software for all available platforms. Review the following considerations before installing OpsCenter components on Windows:

Symantec recommends that you enable 8.3 file name creation before installing OpsCenter components. If 8.3 file name creation is disabled, enable it and restart the Windows host before installing or upgrading to OpsCenter components. You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components.

Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started.

Installing Symantec OpsCenter Server on Windows

Use the following procedure to install Symantec OpsCenter 7.1 server on Windows hosts. Note: In case you try to install OpsCenter 7.1 components on a system where OpsCenter 7.1 is already installed, the installer runs in a Maintenance mode and lets you repair or remove the OpsCenter component that is installed on your system. To install OpsCenter Server on Windows

1 2

On a Windows host where you want to install OpsCenter server, insert the OpsCenter product DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4

On the Symantec DVD browser, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter server.

108

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

5 6 7

The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next. The following options are displayed:
Install to this computer only Select this option to install OpsCenter Server on this host. Install a clustered OpsCenter Select this option to install OpsCenter Server on all Server selected nodes, in a clustered mode. You need to install OpsCenter Server manually on each node of the cluster. This option is enabled if you have Veritas Cluster Server (VCS) installed. See Clustering Symantec OpsCenter on Windows on page 237. See Clustering Symantec OpsCenter Server on Solaris on page 248.

Select Install to this computer only.

In the Installation Method section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required by the installation with the actual space available in the installation directory. Click Custom if you want to change the default settings, locations, or port numbers. Under Custom, you can also select the Upgrade using a backed up VBR or NOM database on a different system option. Select this option if you are upgrading 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 2008. If you have not been using NOM or VBR and are only installing OpsCenter for the first time, you do not need to restore any data. Click Next.

On the License Keys screen, 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. You can also add the license keys later from the OpsCenter console. See About managing licenses on page 307.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

109

10 Click Next. The installer shows the summary of the settings that you have
selected for installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

11 Click Install.
The installer starts installing the OpsCenter Server software. Note: The default OpsCenter database location on Windows is: C:\Program Files\Symantec\OpsCenter\server\db\data

12 After successful installation, you can view the OpsCenter console or view
installation logs.

13 Click Finish.

Installing Symantec OpsCenter Agent on Windows

Use the following procedure to install Symantec OpsCenter Agent on a Windows host. To install OpsCenter Agent

You can install the OpsCenter Agent either on the OpsCenter Server host, product host, or a separate host. To decide where you want to install the OpsCenter Agent, review the information on Agent deployments. See About OpsCenter Agent deployment on page 95.

2 3

On a Windows host where you want to install OpsCenter Agent, insert the OpsCenter product DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

4 5 6 7

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter Agent Installation link to install OpsCenter Agent. The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next.

110

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

The default installation location is C:\Program Files\Symantec. To install OpsCenter to a different directory, click Browse. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. Click Next.

The installer shows the summary of the settings that you have selected for Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

10 Click Install.
The installer starts installation of OpsCenter Agent.

11 After successful installation, you can view Agent installation logs or open
the readme file.

12 Click Finish.

Installing Symantec OpsCenter View Builder on Windows

Use the following procedure to install Symantec OpsCenter View Builder. To install OpsCenter View Builder

1 2

On the OpsCenter Server host, insert the OpsCenter product DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4 5 6

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

111

On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec.

8 9

Select a new location and click Next. The installer shows the summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

10 Click Install.
The installer starts installation of Symantec OpsCenter View Builder.

11 After successful installation, you can view the installation logs or open the
readme file.

12 Click Finish.

Installing Symantec OpsCenter 7.1 on UNIX

This section provides you with the procedure to install OpsCenter on a UNIX host. You can install OpsCenter components from the OpsCenter DVD's. Three DVD's for OpsCenter are available - one for Windows and two for UNIX. Select the appropriate OpsCenter DVD based on the platform on which you are installing. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started.

Installing Symantec OpsCenter Server on UNIX

Use the following procedure to install OpsCenter Server 7.1 software on UNIX hosts. To install OpsCenter Server 7.1 on UNIX

1 2

Open a UNIX console and log on as root on the target host. Mount the appropriate OpsCenter product DVD on the computer where you are installing OpsCenter 7.1.

112

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

Type the following command: ./install. Press Enter. If you are installing OpsCenter on Solaris Sparc, select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

4 5

The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter Server is already installed. The installer also examines the system for existing packages. The installer displays a list of components that get installed like PBX, AT, OpsCenter Server, OpsCenter GUI etc. Review this list and press Enter to continue. The installer prompts you with the following question:
Where do you want to install Symantec OpsCenter? </opt>

Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.

Type y to confirm the directory path and press Enter.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

113

OpsCenter Server is installed on the system. The installer prompts for the following information:
Specify a location for the Symantec OpsCenter database. A directory named 'OpsCenterServer' will be created within the directory that you specify. (/var/symantec/)

Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory, the script creates the folder OpsCenterServer below your directory. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. In case the database installation directory (/var/symantec) does not exist on the host, the following information is displayed:
Directory "/var/symantec" does not exist. Do you want to create the directory? [y,n,q] y

Type y to confirm and press Enter. The following information is displayed:

The OpsCenter database server may require up to 1 GB of temporary space at runtime. By default, temporary files will be created in the database installation directory /var/Symantec/OpsCenterServer

10 You are prompted with the following message:

Would you like to use an alternate directory for database server temporary space? [y,n,q] (n)

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

11 Review the installation options you selected. The location of database directory
and the database temp directory is also displayed.

114

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

12 Type y and press Enter to confirm the selection and continue.

Type n and press Enter to repeat the configuration steps and revise your selection.

13 Configuration changes are made to the system.

You are prompted with the following question:
Do you want to restore data that has been backed up manually using Backup.sh script [y,n,q] <n>

If you have not been using NOM or VBR and are only installing OpsCenter for the first time, you do not need to restore any data. Type n and then press Enter. Use this option if you are upgrading from NOM or VBR to OpsCenter 7.1 server software on a different UNIX system. An example scenario is when NOM or VBR is running on Solaris 8 and you require the same data with OpsCenter 7.1 on Solaris 10. To upgrade on a different server or platform, use Backup.sh script to back up your data on the NOM or VBR server and then copy it to the OpsCenter 7.1 server. The Backup.sh script is located in the Server directory of the OpsCenter DVD. More information on how to upgrade to OpsCenter server on a different system is available. See Upgrading to OpsCenter Server on a different UNIX system on page 206.

14 You are prompted for license information. The installer prompts you with
the following:
Please enter a Symantec OpsCenter Analytics license key or press <Return>:

Enter a valid demo or permanent key that you have received with the purchase of OpsCenter and press Enter. If you do not enter a key, you get an unlicensed version. With the unlicensed version (Symantec OpsCenter), you cannot access the licensed features. See About Symantec OpsCenter Analytics license keys on page 82. You can also add the license keys later from the OpsCenter console. See About managing licenses on page 307.

Installing Symantec OpsCenter Agent on UNIX

Use the following procedure to install OpsCenter Agent on UNIX.

Installing Symantec OpsCenter 7.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. Mount the appropriate OpsCenter product DVD on the computer where you are installing OpsCenter Agent. Type the following command:
./install. Press Enter.

4 5 6 7 8

Select Agent from the displayed options (Server and Agent). Press Enter to install OpsCenter Agent. The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Agent is installed on the system or not. It prompts you in case OpsCenter Agent is already installed. The installer displays a list of components that get installed like PBX, Symantec WebGUI Agent etc. Review this list and press Enter to continue. It is optional to configure the OpsCenter Agent during installation. You may choose to configure OpsCenter Agent later either manually or by running /opt/VRTS/install/installOpsCenterAgent -configure command. Note: The installOpsCenterAgent acript is also present in the Solaris_Sparc64/Agent directory of the DVD. To configure OpsCenterAgent now, type y and press Enter.

Enter the location where you want to install OpsCenter Agent. Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.

10 Type y and then press Enter to confirm your installation options. 11 The OpsCenter Agent is installed. You can view the installation log files,
summary, and response files on the path mentioned.

Installing Symantec OpsCenter silently on Windows

This section lists the procedure on how you can install the OpsCenter components silently on Windows platform. It also lists how you can track the progress of silent installation and some troubleshooting tips.

116

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

Installing OpsCenter silently

A silent installation avoids the need for interactive input. A silent installation uses a response file to automate OpsCenter installation. Use a silent installation when you need to perform an identical installation on several servers. You must create a response file first and then use the file to perform a silent installation. The procedure for creating a response file requires that you run through the Installation Wizard. The values that you specify in the Wizard pages are saved to the response file. You can also edit the response file if required. See About editing the response file on page 133. Note the following points about silent installation:

Silent installation of OpsCenter is only supported on Windows platforms. Silent installation of OpsCenter is not supported on clusters.

To install OpsCenter server software silently

1 2 3

Log on as administrator to the system where you want to install OpsCenter server software. Insert the appropriate OpsCenter product DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\Server directory. Example: D:\x86\Server

Enter the following command:

SETUP.EXE -NoInstall

Note that the switch -NoInstall is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

5 6

The Welcome screen of the Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

117

Select Install to this computer only on the Installation Choice screen. In the Installation Method section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required by the installation with the actual space available in the installation directory. Note: Click Custom if you want to change the default settings, locations, or port numbers. Click Next.

On the License Keys screen, enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. If you do not enter a key, you get an unlicensed version. With the unlicensed version (Symantec OpsCenter), you cannot access the licensed features. See Symantec OpsCenter Administrator's Guide for licensing details. Click Next.

The installer shows the summary of the settings that you have selected for installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install. Note that clicking Install does not install the product.

10 The Installation Status screen is displayed. Click Finish. 11 A response file named Server-<DD-MM-YY-HH-MIN-SS>.XML is created at
the following location: %TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter Server software on multiple machines.

12 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

118

Installing Symantec OpsCenter 7.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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter Server in Add/Remove Programs. To install OpsCenter Agent silently

1 2 3

Log on as administrator to the system where you want to install OpsCenter Agent software. Insert the appropriate OpsCenter product DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\Agent directory. Example: D:\x86\Agent

Enter the following command:

SETUP.EXE -NoInstall

Note that the switch -NoInstall is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

5 6

The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

119

The default installation location is C:\Program Files\Symantec. To install OpsCenter to a different directory, click Browse. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. Click Next.

The installer shows the summary of the settings that you have selected for Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install. Note that clicking Install does not install the product.

10 The Installation Status screen is displayed. Click Finish. 11 A response file named Agent-<DD-MM-YY-HH-MIN-SS>.XML is created at the
following location: %TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter Agent software on multiple machines.

12 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter Agent in Add/Remove Programs.

120

Installing Symantec OpsCenter 7.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. Insert the appropriate OpsCenter product DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\ViewBuilder directory. Example: D:\x86\ViewBuilder

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

5 6 7

The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next. The default installation location is C:\Program Files\Symantec. To install OpsCenter View Builder to a different directory, click Browse. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. Click Next.

The installer shows the summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

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

10 The Installation Status screen is displayed. Click Finish. 11 A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>.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.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

121

12 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter View Builder in Add/Remove Programs.

Upgrading silently from NOM and VBR to OpsCenter

Use the following procedures to upgrade to OpsCenter components silently. To upgrade silently from NOM or VBR to OpsCenter 7.1 Server

1 2 3

Log on as administrator to the NOM system or VBR system where you want to install OpsCenter server software. Insert the appropriate OpsCenter DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\Server directory. Example: D:\x86\Server

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

122

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

The Installation Wizard detects an existing installation of NetBackup Operations Manager or Veritas Backup Reporter on the system. For example, the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: NetBackup Operations Manager Server: Version 6.5 Before you upgrade to Symantec OpsCenter, all existing NOM services are stopped automatically. After you successfully upgrade to Symantec OpsCenter, you can manually uninstall NOM. Click Next.

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. In the Installation Method section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required for installing OpsCenter server and the actual space that is available. Click Next. Note: Click Custom if you want to change the default settings, locations, or port numbers.

Specify a location for saving the old NOM or VBR database. The default location is C:\Program Files\Symantec\OpsCenter\SavedData. Click Browse to specify a different location. Click Next. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.

On the Upgrade Settings page, enter a port number on which the old NOM or VBR database can be started. The default port number is 13799. Click Next.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

123

10 On the License Keys screen, enter your demo or permanent key that you have
received with the purchase of OpsCenter and click Add Key. If you are upgrading from NOM and you do not enter a key, you get an unlicensed version (Symantec OpsCenter). With an unlicensed version, you cannot access the licensed features. If you are upgrading from VBR and you do not enter a license key, your existing license keys are used. The license keys that are already installed on the system are displayed in the box that appears on this screen. The license type information is also shown along with the key. See the Symantec OpsCenter Administrators Guide for more information about licenses. Click Next.

11 The installer shows a summary of the settings that you have selected for
installation. Check Save Summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install. Note that clicking Install does not install the product.

12 The Installation Status screen is displayed. Click Finish. 13 A response file named Server-<DD-MM-YY-HH-MIN-SS>.XML is created at the
following location: %TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter server software on multiple machines.

14 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

124

Installing Symantec OpsCenter 7.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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter Server in Add/Remove Programs. To upgrade silently from VBR Agent to OpsCenter 7.1 Agent

1 2 3

Log on as administrator to the VBR Agent system that you want to upgrade to OpsCenter server software. Insert the appropriate OpsCenter DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\Agent directory. Example: D:\x86\Agent

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case-sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

125

The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of Veritas Backup Reporter Agent on the system. Based on your installed VBR Agent version, the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Veritas Backup Reporter Agent: <Version> Before you upgrade to Symantec OpsCenter Agent, all Veritas Backup Reporter services are stopped automatically. After you successfully upgrade to Symantec OpsCenter Agent, you must manually uninstall Veritas Backup Reporter Agent. Click Next to continue.

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter Agent installation. Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space. Select a new location and click Next.

The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install. Note that clicking Install does not install the product.

The Installation Status screen is displayed. Click Finish. following location:

%TEMP%\Symantec\OpsCenter\

10 A response file named Agent-<DD-MM-YY-HH-MIN-SS>.XML is created at the

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

11 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

126

Installing Symantec OpsCenter 7.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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter Agent in Add/Remove Programs. To upgrade silently from VBR View Builder to OpsCenter 7.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. Insert the appropriate OpsCenter DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\ViewBuilder directory. Example: D:\x86\ViewBuilder

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing Veritas Backup Reporter View Builder and shows the following message on the Welcome page: The Installation has detected that the following software is already installed on your system: Veritas Backup Reporter View Builder: <version>. In order to upgrade to a newer version, the existing Veritas Backup Reporter View Builder will be removed.' Click Next to continue.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

127

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space. Select a new location and click Next.

The installer shows a summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install.

A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>.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.

10 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

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.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter View Builder in Add/Remove Programs.

Upgrading silently from OpsCenter 7.0 and 7.0.1 to OpsCenter 7.1

Use the following procedures to upgrade to OpsCenter components silently.

128

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

To upgrade from OpsCenter 7.0 Server or OpsCenter 7.0.1 Server to OpsCenter 7.1 Server

1 2 3

Log on as administrator to the OpsCenter 7.0 or 7.0.1 system that you want to upgrade to OpsCenter 7.1. Insert the appropriate OpsCenter DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\Server directory. Example: D:\x86\Server

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

The Installation Wizard detects an existing installation of OpsCenter 7.0 or 7.0.1 on the system. For example, the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter Server: Version 7.0 In order to upgrade to a newer version, the existing Symantec OpsCenter Server will be removed. Click Next.

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. In the Installation Method section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required for installing OpsCenter server and the actual space that is available. Click Next. Note: You cannot customize the default settings, locations, or port numbers while upgrading from OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

129

Specify a location for saving the old OpsCenter 7.0 or 7.0.1 database. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. Click Browse to specify a different location. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist, you are prompted to create it. Click Yes to create the directory. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.

On the License Keys screen, 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. Click Next.

10 The installer shows a summary of the installation settings.

Check Save Summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install. Note that clicking Install does not install the product.

11 The Installation Status screen is displayed. Click Finish. 12 A response file named Server-<DD-MM-YY-HH-MIN-SS>.XML is created at the
following location: %TEMP%\Symantec\OpsCenter This XML file can be used to upgrade OpsCenter Server software on multiple machines.

13 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

130

Installing Symantec OpsCenter 7.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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter Server 7.1 in Add/Remove Programs. To upgrade silently from OpsCenter 7.0 or 7.0.1 Agent to OpsCenter 7.1 Agent

1 2 3

Log on as administrator to the OpsCenter Agent system that you want to upgrade. Insert the appropriate OpsCenter DVD in the DVD drive. Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\Agent directory. Example: D:\x86\Agent

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case-sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of OpsCenter 7.0 pr 7.0.1 Agent on the system. 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.0 In order to upgrade to a to a newer version, the existing Symantec OpsCenter Agent will be removed. Click Next to continue.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

131

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install. Note that clicking Install does not install the product.

8 9

The Installation Status screen is displayed. Click Finish. A response file named Agent-<DD-MM-YY-HH-MIN-SS>.XML is created at the following location:
%TEMP%\Symantec\OpsCenter\

This XML file can be used to upgrade OpsCenter 7.0 or 7.0.1 Agent software on multiple machines.

10 On the command prompt, ensure that you are in the directory where
SETUP.EXE is located.

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.xml Note that the switches -Silent and -RespFile are case sensitive.

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. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, you can see Symantec OpsCenter Agent 7.1 in Add/Remove Programs. To upgrade silently from OpsCenter 7.0 or 7.0.1 View Builder to OpsCenter 7.1 View Builder

1 2

Log on as administrator to the OpsCenter View Builder system that you want to upgrade. Insert the appropriate OpsCenter DVD in the DVD drive.

132

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\ViewBuilder directory. Example: D:\x86\ViewBuilder

Enter the following command:

SETUP.EXE -NoInstall

Note that the -NoInstall switch is case sensitive. This command starts the Installation Wizard where you can specify your preferences. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

The Symantec OpsCenter Installation Wizard appears. 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.0 In order to upgrade to a to a newer version, the existing Symantec OpsCenter View Builder will be removed. Click Next to continue.

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. The installer shows a summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install.

A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>.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.

On the command prompt, ensure that you are in the directory where SETUP.EXE is located.

Installing Symantec OpsCenter 7.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.xml

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

11 The installation logs are generated at the following location:

%ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS

See the following section to track the progress of the installation. See About tracking the progress of silent installation and troubleshooting tips on page 134. After successful installation, 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 . The silent installation is based on these inputs. To edit the response file, open it and modify the Value field for the applicable install property. For example, you can modify the OpsCenter installation location, license key information, or database directory in the response file. The following are the contents of a sample response file:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> - <XML_Install> - <OpsCenter_Server> <InstallProperty Name="RAN_SETUP" Value="1" /> <InstallProperty Name="INSTALLDIR" Value="C:\Program Files\Symantec" /> <InstallProperty Name="BUSINESS_REP_LIC_KEYS"> <TagValue><License Key></TagValue> </InstallProperty> <Installproperty Name="SCMSTARTTYPE" Value="auto" /> <Installproperty Name="INSTALLPBX" Value="YES" /> <Installproperty Name="STARTSERVICE" Value="YES" /> <Installproperty Name="DATABASE_DATA_DIR" Value="C:\Program Files\Symantec\ </OpsCenter_Server> </XML_Install>

For example, you can modify the OpsCenter installation location in this response file by changing the value of INSTALLDIR property from C:\Program

134

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

Files\Symantec to D:\Symantec. You can also modify the database directory by modifying the value of the DATABASE_DATA_DIR property. Similarly you can edit the license key by changing the value of BUSINESS_REP_LIC_KEYS property. You can also add a new license key by adding <TagValue>License key </TagValue> under <InstallProperty Name="BUSINESS_REP_LIC_KEYS" >. Note that the text that you enter or modify in the response file is case sensitive. You must save the response file after you modify it. Note: Symantec recommends that you do not change the value of RAN_SETUP, SCMSTARTTYPE, INSTALLPBX, and STARTSERVICE properties.

About tracking the progress of silent installation and troubleshooting tips

When a silent installation is in progress, you can see SETUP.EXE process running in the Processes tab of the Windows Task Manager. In addition, you will also find multiple msiexec.exe processes running in the Task Manager. You can also track if a silent installation is in progress by checking the size of Vxinst.log file. The size of Vxinst.log file increases as silent installation progresses. The Vxinst.log file is generated in %ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.

About troubleshooting silent installation issues

Use the following procedure to troubleshoot silent installation issues. This procedure must be performed after the silent installation ends. To troubleshoot silent installation issues

After the silent installation ends, navigate to the following location:

%ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.

Check if a file named OpsCenterInstallLog.htm is present. If OpsCenterInstallLog.htm is not present, see 7.

Installing Symantec OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX

135

Open OpsCenterInstallLog.htm and check the timestamp and the OpsCenter component it is for to ensure that it is the appropriate log file. You must check the timestamp because OpsCenterInstallLog.htm may have been generated as a result of previous silent installations. In addition, the same OpsCenterInstallLog.htm file is generated when you install OpsCenter server, Agent, or View Builder. Hence you must check the specific OpsCenter component that is associated with OpsCenterInstallLog.htm.

You can check the timestamp by opening OpsCenterInstallLog.htm and seeing the first line in the file. For example, the following is the first line from a sample OpsCenterInstallLog.htm file:
01-19-2010,13:35:30: -Silent _RespFile "C:\Documents and Settings\Administrator\Agent-19-01-10-13-04-21.xml"

In this example, the timestamp is 01-19-2010, 13:35:30.

To know the OpsCenter component the log file is associated with, search for the following keywords in the OpsCenterInstallLog.htm file:
OpsCenter Server You will find matches when you search for OpsCenter Server in the file. This means that the log file is for OpsCenter server. You will find matches when you search for OpsCenter Agent in the file. This means that the log file is for OpsCenter Agent. You will find matches when you search for OpsCenter View Builder in the file. This means that the log file is for OpsCenter View Builder.

OpsCenter Agent

OpsCenter View Builder

Note: In case you have checked the timestamp and the OpsCenter component associated with all OpsCenterInstallLog.htm files that are present and do not find a valid OpsCenterInstallLog.htm file, see 7.

136

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Use the OpsCenterInstallLog.htm file to troubleshoot silent installation issues. Open the OpsCenterInstallLog.htm file to see if the installation was successful or to understand why the installation failed. This file shows the installation status at the end. Installation errors are flagged in this file in red color. You may also see a description about why the error occurred and troubleshoot accordingly. Ignore the subsequent steps of this procedure.

If OpsCenterInstallLog.htm is not present or you cannot find a valid OpsCenterInstallLog.htmfile, check if OpsCenter<Product>InstallLog.htm file is present. In OpsCenter<Product>InstallLog.htm, <Product> can be Server, Agent, or View Builder depending on the OpsCenter component that you are installing. Always ensure that the OpsCenter<Product>InstallLog.htm file is appropriate by checking the timestamp. You can check the timestamp by opening the OpsCenter<Product>InstallLog.htm file and seeing the first line of the file. For example, the following is the first line from a sample OpsCenter<Product>InstallLog.htm file:
01-19-2010,13:35:30: -Silent _RespFile "C:\Documents and Settings\Administrator\Agent-19-01-10-13-04-21.xml"

In this example, the timestamp is 01-19-2010, 13:35:30.

Use the OpsCenter<Product>InstallLog.htm file to troubleshoot silent installation issues. You can open the OpsCenter<Product>InstallLog.htm file to see if the installation was successful or to understand why the installation failed. This file shows the installation status at the end. Installation errors are flagged in this file in red color. You may also see a description about why the error occurred and troubleshoot accordingly.

Upgrading to OpsCenter on Windows and UNIX

This section describes how you can upgrade from OpsCenter 7.0 or 7.0.1, NOM, or VBR to OpsCenter 7.1 on Windows and UNIX platforms.

Upgrading from OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1

Use the following procedure to upgrade OpsCenter 7.0 components to OpsCenter 7.1 on Windows and UNIX hosts.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

137

Note: If there are special characters in a report name like (/ \ * ? | "), these special characters are replaced with an underscore '_' when you upgrade to OpsCenter 7.1. For example a media**summary report in OpsCenter 7.0 is renamed as media__summary report in OpsCenter 7.1.

Upgrading from OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1 on Windows

Use the following procedure to upgrade OpsCenter 7.0 or 7.0.1 components to OpsCenter 7.1 on Windows hosts. Review the following considerations before installing OpsCenter components on Windows:

Symantec recommends that you enable 8.3 file name creation before installing OpsCenter components. If 8.3 file name creation is disabled, enable it and restart the WIndows host before installing or upgrading to OpsCenter components. You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components. Symantec recommends that you do not cancel or interrupt the installation process once it is started. In case you try to install OpsCenter 7.1 components on a system where OpsCenter 7.1 is already installed, the installer runs in a Maintenance mode and lets you repair or remove the OpsCenter 7.1 component that is installed on your system.

To upgrade from OpsCenter Server 7.0 or 7.0.1 to OpsCenter Server 7.1

1 2

On a Windows host where you want to install OpsCenter Server, insert the appropriate OpsCenter product DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server.

138

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

The Welcome Page of the Installation Wizard appears. The Installation Wizard detects an existing installation of OpsCenter Server 7.0 (or 7.0.1) on the system. Depending on the installed 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 Server: Version 7.0 In order to upgrade to a newer version, the existing Symantec OpsCenter Server will be removed. Click Next to continue.

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Choice section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required for installing OpsCenter Server and the actual space that is available. Note: You cannot customize the default settings, locations, or port numbers while upgrading from OpsCenter 7.0 (or 7.0.1) to OpsCenter 7.1. Click Next.

Specify a location for saving the old OpsCenter database. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. Click Browse to specify a different location. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist, you are prompted to create it. Click Yes to create the directory. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.

On the License Keys screen, enter your demo or permanent key that you have received with the purchase of OpsCenter 7.1 and click Add Key. See About Symantec OpsCenter Analytics license keys on page 82.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

139

10 The installer shows the summary of the installation settings. Check Save
summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install to begin the installation. The installer installs OpsCenter Server 7.1 software and also migrates data from OpsCenter 7.0 (or 7.0.1) to the OpsCenter 7.1 database. The database migration may take some time based on the size of your database.

11 After successful installation, you can view the installation logs or view the
Readme. Click Finish. The installation logs are generated in the following location:
%ALLUSERSPROFILE%\Symantec\OpsCenter\ INSTALLLOGS\OpsCenterServerInstallLog.htm

To upgrade from OpsCenter Agent 7.0 or 7.0.1 to OpsCenter Agent 7.1

1 2

On a Windows host where you want to install OpsCenter Agent, insert the OpsCenter product DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4 5

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter Agent Installation link to install Symantec OpsCenter Agent 7.1. The Welcome Page of the Installation Wizard appears. The Installation Wizard detects an existing installation of OpsCenter Agent 7.0 (or 7.0.1) on the system. Depending on the installed 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.0 In order to upgrade to a to a newer version, the existing Symantec OpsCenter Agent will be removed. Click Next to continue.

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

140

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

The installer shows the summary of the installation settings. Check Save summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install to begin the installation. The installer installs OpsCenter Agent 7.1 software.

After successful installation, you can view the installation logs or view the Readme. Click Finish. The installation logs are generated in the following location:
%ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS\OpsCenterAgentInstallLog.htm

To upgrade from OpsCenter View Builder 7.0 or 7.0.1 to OpsCenter View Builder 7.1

1 2

On a Windows host where you want to install OpsCenter View Builder, insert the OpsCenter product DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4 5

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder 7.1. The Welcome Page of the Installation Wizard appears. The Installation Wizard detects an existing installation of OpsCenter View Builder 7.0 (or 7.0.1) on the system. Depending on the installed version, 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.0 In order to upgrade to a to a newer version, the existing Symantec OpsCenter View Builder will be removed. Click Next to continue.

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

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

141

The installer shows the summary of the installation settings. Check Save summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location. Click Install to begin the installation. The installer installs OpsCenter View Builder 7.1 software.

After successful installation, you can view the installation logs or view the Readme. Click Finish. The installation logs are generated in the following location:
%ALLUSERSPROFILE%\Symantec\OpsCenter\ INSTALLLOGS\OpsCenterViewBuilderInstallLog.htm

Upgrading from OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1 on UNIX

Use the following procedure to upgrade from OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1 software on UNIX hosts. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. To upgrade from OpsCenter 7.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. Mount the OpsCenter product DVD on the OpsCenter 7.0 (or 7.0.1) Server that you want to upgrade. Type the following command: ./install. Press Enter. If you are installing OpsCenter on Solaris Sparc, select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

4 5

The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter Server is already installed. The installer also examines the system for existing packages.

142

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

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. (/var/symantec/)

Type the directory name in which the existing OpsCenter 7.0 database and configuration files can be saved and then press Enter. To accept the default directory path (/var/symantec), press Enter.

The installer displays a list of components that will be installed or upgraded like PBX, AT, OpsCenter Server, OpsCenter GUI etc. Review this list and press Enter to continue. 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.

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.

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

system.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

143

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

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

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

To upgrade from OpsCenter 7.0 or 7.0.1 Agent to OpsCenter 7.1 Agent on UNIX

1 2 3

Open a UNIX console and log on as root on the target host. Mount the OpsCenter product DVD on the OpsCenter Agent 7.0 (or 7.0.1) computer that you want to upgrade to OpsCenter 7.1.. Type the following command:
./install. Press Enter.

4 5 6 7

Select Agent from the displayed options (Server and Agent). Press Enter to install OpsCenter Agent. The Welcome message is displayed. Press Enter to continue. The installer checks if OpsCenter Agent is installed. The installer displays that OpsCenter Agent 7.0 (or 7.0.1) is installed. The installer displays the packages that are installed like PBX, Symantec OpsCenter Agent etc. Press Enter to install or upgrade these packages to 7.1. It then uninstalls packages with older versions and installs 7.1 packages.

OpsCenter Agent 7.1 is installed. You can view the installation log and summary files on the path mentioned.

144

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Upgrading from NetBackup Operations Manager to Symantec OpsCenter 7.1 on Windows and UNIX
The following upgrade paths are supported when you upgrade from NOM to OpsCenter 7.1:

NOM 6.5.4 -> OpsCenter 7.1 NOM 6.5.6 -> OpsCenter 7.1

The OpsCenter Installation Wizard automatically detects an older NOM installation. The OpsCenter installer only stops the existing NOM services. It does not uninstall your existing NOM installation. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time. During upgrade, OpsCenter server is installed, the older NOM database is saved and started. Note that a saved copy of the NOM database is used for upgrade. Data migration from the older NOM database to the new OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter server. You can access the data migration status page from the OpsCenter logon page. The data migration process may take time depending on the volume of data that has to be migrated.

About NOM upgrade considerations

When you upgrade from NOM to OpsCenter 7.1, the Disk Usage report displays a data mismatch in comparison to the report in OpsCenter. The reason is that, in NOM, job count calculation is based on the StartTime parameter where as in OpsCenter 7.1 the calculation is based on the EndTime parameter. These changes produce different values of jobs in NOM and OpsCenter so the values of throughput, activity duration, and % utilization are different in both.

Starting data collection when you configure OpsCenter Agent after upgrading from NOM to OpsCenter 7.1
When you upgrade from NOM to OpsCenter Server 7.1 and configure the OpsCenter Agent after upgrade, data collection does not start for Images, Error Logs, SubJobs (or Breakup Jobs), and Scheduled Jobs. The data collection status for Image, Error Logs, Breakup Jobs, and Scheduled Jobs is shown as Not Started or Not Reported. Use the following procedure to resolve this issue. This procedure must be repeated for all master servers. To start data collection for Images, Error Logs, SubJobs, and Scheduled Jobs

1 2

On the OpsCenter console, click Settings > Configuration > NetBackup. Select the master server and click Edit.

Installing Symantec OpsCenter 7.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. No Agent should be selected. Click Save. On the Settings > Configuration > NetBackup page, select the master server again and click Edit. Select the desired Agent from the Agent drop-down list. Click Save.

Upgrading from NetBackup Operations Manager to Symantec OpsCenter 7.1 on Windows

Use the following procedure to upgrade to OpsCenter server on Windows. Review the following considerations before installing OpsCenter components on Windows:

Symantec recommends that you enable 8.3 file name creation before installing OpsCenter components on Windows. If 8.3 file name creation is disabled, enable it and restart the Windows host before installing or upgrading to OpsCenter components. You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components. Symantec recommends that you do not cancel or interrupt the installation process once it is started.

To upgrade from NOM to Symantec OpsCenter 7.1 on Windows

1 2

On a Windows host where you want to install OpsCenter server, insert the appropriate OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server 7.1.

146

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of NetBackup Operations Manager on the system. For example, the following message may be displayed on the Welcome screen:
The Installation has detected that the following software is already installed on your system: Veritas NetBackup Operations Manager Release Update 4: Version 6.5.4

Before you upgrade to OpsCenter 7.1, all existing NOM services are stopped automatically. After you successfully upgrade to OpsCenter 7.1, you can manually uninstall NOM. Information is available on how to configure and restart NOM. See Reusing NOM after upgrading to OpsCenter on Windows on page 147.

6 7 8

Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Choice section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required for installing OpsCenter Server and the actual space that is available. Note: Click Custom if you want to change the default settings, locations, or port numbers. Click Next.

Specify a location for saving the old NOM database. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. Click Browse to specify a different location. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist, you are prompted to create it. Click Yes to create the directory. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.

10 On the Upgrade Settings page, enter a port number on which the old NOM
database can be started. The default port number is 13799. Click Next.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

147

11 On the License Keys screen, enter your demo or permanent key that you have
received with the purchase of OpsCenter 7.1 and click Add Key. See About Symantec OpsCenter Analytics license keys on page 82.

12 Click Next. The installer shows the summary of the settings that you have
selected for installation. Check Save Summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location.

13 Click Install.
The installer installs OpsCenter Server software.

14 After successful installation, you can view the OpsCenter console or view
installation logs. Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. You can also access the data migration status from the OpsCenter console. See Monitoring data migration from NOM to Symantec OpsCenter on page 169.

15 Click Finish. Reusing NOM after upgrading to OpsCenter on Windows

After you upgrade from NOM to OpsCenter 7.1 on Windows, the NOM processes are stopped. In case you want to reuse NOM after upgrading to OpsCenter 7.1, the following steps help you to restart NOM.

148

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

To restart NOM services after upgrading to OpsCenter 7.1 on Windows

Run the following command to enable VxPBX.

C:\Program Files\Veritas\Security\Authentication\bin>vssat setispbxexchflag -enable

Run the following command to delete the domain NOM_MACHINES from the system.
C:\Program Files\Veritas\Security\Authentication\bin>vssat deletepd --pdrtype ab --domain NOM_MACHINES@<system name>

Run the following command to delete the broker domain vx:domain name.
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, restart the pbx services and vxat services. Restarting the services helps in restarting the NOM manager. Once the NOM manager is up, you can start the NOM GUI.

Upgrading from NetBackup Operations Manager to OpsCenter on UNIX

Use the following procedure to upgrade from NOM to OpsCenter Server 7.1 on UNIX. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. To upgrade from NOM to OpsCenter Server 7.1 on UNIX

1 2 3

Open a UNIX console and log on as root on the target host. Mount the OpsCenter product DVD on the computer that you want to upgrade to OpsCenter 7.1. Type the following command: ./install. Press Enter. If you are installing OpsCenter on Solaris Sparc, select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

4 5

Type the following command:./installOpsCenterServer. Press Enter. The Welcome message is displayed. Press Enter to continue.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

149

The installer then checks for an existing NOM installation. It displays the following message when NOM is installed:
NetBackup Operations Manager (NOM) <version> is installed on <hostname>. Do you want to upgrade from NOM <version> to Symantec OpsCenter [y,n,q] y

To upgrade to Symantec OpsCenter Server 7.1, type y and then press Enter. Note: In case you try to upgrade from an unsupported NOM version like 6.5.3 to OpsCenter 7.1, the installer displays the following message: NetBackup Operations Manager (NOM) 6.5.3 is installed on <host>. It is recommended that you upgrade to Symantec OpsCenter 7.1 from NOM 6.5.4 or a higher version. Do you want to upgrade from NOM 6.5.3 to Symantec OpsCenter 7.1? [y,n,q] (n)

The following message is displayed:

The existing NOM database and configuration files must be backed up before upgrading to Symantec OpsCenter. Where should the NOM database and configuration files be backed up? An OpsCenter_save directory will be created within the directory that you specify to store these files. (/var/symantec)

Type the directory name in which the NOM database and configuration files can be saved and then press Enter. To accept the default directory path (/var/symantec), press Enter.

The installer displays a list of components that get installed like PBX, AT, OpsCenter Server, OpsCenter GUI etc. Review this list and press Enter to continue. The installer prompts for the following information:
Where do you want to install Symantec OpsCenter? (/opt)

Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.

10 Type y to confirm the directory path and press Enter.

150

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

11 OpsCenter Server is installed on the system.

The installer prompts for the following information:
Specify a location for the Symantec OpsCenter database. A directory named 'OpsCenterServer' will be created within the directory that you specify. (/var/symantec/)

Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory, the script creates the folder OpsCenterServer below your directory. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. In case the database installation directory (/var/symantec) does not exist on the host, the following information is displayed:
Directory "/var/symantec" does not exist. Do you want to create the directory? [y,n,q] y

Type y to confirm and press Enter. The following information is displayed:

The OpsCenter database server may require up to 1 GB of temporary space at runtime. By default, temporary files will be created in the database installation directory, /var/Symantec/OpsCenterServer

12 You are prompted with the following message:

Would you like to use an alternate directory for database server temporary space? [y,n,q] (n)

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

13 Review the installation options you selected. The location of database directory
and the database temp directory is also displayed.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

151

14 Type y and press Enter to confirm the selection and continue.

Type n and press Enter to repeat the configuration steps and revise your selection.

15 Configuration changes are performed. You are prompted with the following
message:
The old database will be started separately to migrate its data to the OpsCenter database. Specify a port number on which the old database can be started (13799)

Type a port number on which the old NOM database can be started and press Enter. To accept the default port number (13799), press Enter only. Note: Ensure that the port number that you enter is free and not used by any application.

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, type the license key and press Enter. If you do not enter any key and press Enter, you get an unlicensed version (Symantec OpsCenter). You cannot access the licensed features by using the unlicensed version.

17 All the OpsCenter services are started. The NOM processes are stopped after
OpsCenter Server is installed. Information is available on how to configure and restart NOM. See Restarting NOM after upgrading to OpsCenter 7.1 Server on page 152. The following information is also displayed:

Web URL to access the OpsCenter console. Location of install log, summary, and response files. Link on the OpsCenter logon page from where you can access the data migration status Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. You can also access the data migration status from the OpsCenter console.

152

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

See Monitoring data migration from NOM to Symantec OpsCenter on page 169.

Restarting NOM after upgrading to OpsCenter 7.1 Server

After you upgrade from NOM to OpsCenter 7.1 on UNIX, the NOM processes are stopped. In case you still want to use NOM after upgrading to OpsCenter 7.1, use the following steps to start NOM on UNIX platforms. To restart NOM after upgrading to OpsCenter 7.1 on UNIX

Navigate to the following directory depending on the specific UNIX platform:

Solaris Linux cd /etc/init.d cd /etc/rc.d/init.d/

Run the following commands to restore the NOM server processes:

mv vxnomd_NOM vxnomd mv vxnomweb_NOM vxnomweb

Navigate to the following directory:

cd /opt/VRTSnom/bin/

Run the following command to restart all NOM processes.

./NOMAdmin -start_service

Upgrading from Veritas Backup Reporter to OpsCenter Analytics 7.1 on Windows and UNIX
The following upgrade paths are supported when you upgrade from VBR to OpsCenter 7.1:

VBR 6.6.1 -> OpsCenter 7.1 VBR 6.6.2 -> OpsCenter 7.1

The OpsCenter Installation Wizard automatically detects an older VBR installation. The OpsCenter installer only stops the existing VBR services. It does not uninstall your existing VBR installation. Do not uninstall VBR server after upgrading successfully to Symantec OpsCenter server software on a Windows platform. Read the following TechAlert if you want to uninstall VBR on Windows: http://www.symantec.com/business/support/index?page=content&id=TECH126226

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

153

During upgrade, OpsCenter is installed and the older VBR database is saved and started. Note that a saved copy of the VBR database is used for upgrade. The data migration from the older VBR database to the new OpsCenter database starts after you successfully upgrade to OpsCenter. The data migration process happens for each master server. You can also view the data migration process from the OpsCenter logon page. The data migration process may take time depending on the data that has to be migrated.

About VBR upgrade considerations

Review the following considerations about upgrading from VBR to OpsCenter 7.1 Server:

After upgrading from VBR to OpsCenter 7.1 Server, data is not displayed under Monitor > Devices, Manage > Storage, and Manage > Devices. After a VBR upgrade, data is not displayed under the Storage and Devices tabs in Monitoring. (Storage units, Robots, Drives, and so forth.) The data is not displayed as VBR does not collect any monitoring data, only the names are provided from the job records. This data is collected from the master server after the upgrade as part of the regular data collection. If a VBR server that collects NetBackup data through a remote VBR Agent is upgraded to OpsCenter 7.1 Server, then after upgrade you must first configure the master servers to allow server access and data collection by OpsCenter. See Adding a master server in OpsCenter on page 377. If you uninstall VBR after upgrading from VBR to OpsCenter 7.1 Server on Solaris, then you may not be able to log on to the OpsCenter console. To resolve this issue, you must start the AT process manually by running /opt/VRTSat/bin/vxatd. In case you have changed the default database passwords (dba, guest, ccsvc) or database port numbers for VBR, you must reset these to the default values before upgrading to OpsCenter 7.1. See About upgrading from VBR to OpsCenter Server 7.1 if you use customized database passwords or port numbers in VBR on page 154.

When you upgrade from VBR, or 7.0, or 7.0.1 to OpsCenter 7.1, some reports display a data mismatch in comparison to the reports in OpsCenter. The reason for this mismatch is the filters applied to these reports.

The Consecutive Failures, All Failed Backups, Success Rate Line, and Advanced Success Analysis reports display mismatched data when you apply the Full Window Parameter and Full for Duration of (In hours) filters. The default value for Full Window Parameter is 12 A.M. and for Full for Duration of (In hours),

154

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

the value is 24 hrs. When you use the default filters, the report displays data for all jobs. The report data however changes when you change the filter values. For example, if you consider 12 A.M. for Full Window parameter and 15 hours for Full for Duration of (In hours) filters, the report displays the data for the jobs that run between 12 A.M. to 3 P.M. (15-hrs window ). In OpsCenter the correct data is displayed but VBR displays incorrect data. Though you specify the filter values, VBR displays data for all the jobs that run for 24 hours. This issue is fixed for OpsCenter.

The Consecutive Failures, All Failed Backups, Success Rate Line, and Advanced Success Analysis reports display mismatched data when you apply the Schedule Type/Level filter. In VBR, when you apply the Schedule Type/Level filter with the value All, the report displays data for all types of jobs. The data displayed is incorrect as the report should display data only for Full and Incremental jobs. This issue is fixed in OpsCenter. The Consecutive Failures report displays data mismatch as VBR miscalculates the data. For example, if the filter value for consecutive failures is 3, the report should display data for all the jobs that consecutively failed 3 times. However VBR report shows jobs that have failed only once. It does not consider the consecutive failures filter. The Client Risk Analysis report might display data mismatch, 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. This issue is fixed for OpsCenter. The Forecast report in OpsCenter 7.0 and 7.0.1 displays a mismatch in comparison to the report in OpsCenter 7.1. The reason for mismatch is that , the forecast calculation in opscenter 7.0/7.0.1 was wrongly calculated. This issue is fixed for OpsCenter. The media reports such as Tape Expiring Now, Tape Expiring in the Future, and Tape Count are affected as a result of additional the filters added in OpsCenter 7.0.1. TReport ignores data for Media types Backup to Disk, Blank Media , Optical Disk Readwriteable , Optical Disk Worn. The reports do not display the data for these parameters as implicit filters are added to the Media Type filter.

About upgrading from VBR to OpsCenter Server 7.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, you must reset these to the default values before upgrading to OpsCenter Server 7.1. For example, you may have changed the database admin password (dba), guest password (guest), database passwords for members of the ccsvc_user account (ccsvc) or the database port number in VBR.

Installing Symantec OpsCenter 7.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. To change VBR passwords and port numbers to default values

Reset all custom VBR database passwords and database port numbers to the default values. See the VBR documentation for more information.

Clear the contents of vbr_conf.properties file. The vbr_conf.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, Agent, and View Builder to Symantec OpsCenter Server, Agent, and View Builder respectively. Review the following considerations before installing OpsCenter components on Windows:

Symantec recommends that you enable 8.3 file name creation before installing OpsCenter components. If 8.3 file name creation is disabled, enable it and restart the WIndows host before installing or upgrading to OpsCenter components. You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components. Symantec recommends that you do not cancel or interrupt the installation process once it is started.

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.

156

Installing Symantec OpsCenter 7.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, insert the appropriate OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4 5

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server. The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of Veritas Backup Reporter on the system. For example, the following message may be displayed on the Welcome screen:
The Installation has detected that the following software is already installed on your system: Veritas Backup Reporter Server: Version 6.6.1 Before you upgrade to OpsCenter 7.1, all existing VBR server services are stopped automatically. After you successfully upgrade to Symantec OpsCenter, you must manually uninstall VBR server software.

Note that you should not uninstall VBR server after upgrading successfully to Symantec OpsCenter server software. Read the following TechAlert if you want to uninstall VBR after upgrading to OpsCenter server: http://www.symantec.com/business/support/index?page=content&id=TECH126226

6 7

Click Next to continue. Read the license agreement, check I accept the terms of the license agreement and click Next.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

157

On the Installation Choice section, click Typical to use the default settings, installation location, or port numbers. Also compare the space that is required for upgrading to OpsCenter 7.1 and the actual space that is available. Note: Click Custom if you want to change the default settings, locations, or port numbers. Click Next.

Specify a location for saving the old VBR database. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. Click Browse to specify a different location. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space. Click Next to continue. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist, you are prompted to create it. Click Yes to create the directory.

10 On the Upgrade Settings page, enter a port number on which the old VBR
database can be started. The default port number is 13799. Note: Ensure that the port number that you enter is free and not used by any other application. Click Next.

11 On the License Keys screen, enter the demo or permanent key that you have
received with the purchase of OpsCenter and click Add Key. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. The license type is also shown along with the key. If you do not enter a license key, your existing license keys are used. See About Symantec OpsCenter Analytics license keys on page 82.

158

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

12 Click Next. The installer shows the summary of the settings that you have
selected for installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

13 Click Install.
The installer upgrades VBR server to OpsCenter Server 7.1.

14 After successful installation, you can view the OpsCenter console or view
installation logs. Data migration from the old VBR database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter Server 7.1. You can also access the data migration status from the OpsCenter console. See Monitoring data migration from VBR to Symantec OpsCenter Analytics 7.1 on page 186.

15 Click Finish. Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent on Windows
Use the following procedure to upgrade from Veritas Backup Reporter Agent to Symantec OpsCenter Agent. You do not require an OpsCenter Agent to collect data from NetBackup 7.0 and later versions or PureDisk. However, you must install OpsCenter Agent if you want to collect data from other backup products. Note: Once you upgrade your VBR Agent to the OpsCenter Agent, the port number that the VBR Agent uses is not required in OpsCenter. By default, the VBR Agent uses port number 7806. To upgrade to OpsCenter Agent on Windows

1 2

On a Windows host where you want to install OpsCenter Agent, insert the appropriate OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

On the Symantec DVD Browser, click the Installation link.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

159

4 5

Click the OpsCenter Agent Installation link to install Symantec OpsCenter Agent. The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of Veritas Backup Reporter Agent on the system. Based on your installed VBR Agent version, the following message may be displayed on the Welcome screen:
The Installation has detected that the following software is already installed on your system: Veritas Backup Reporter Agent: <Version> It is recommended that you upgrade to Symantec OpsCenter Agent 7.1 from VBR 6.6.1 or a higher version

Before you upgrade to Symantec OpsCenter Agent, all Veritas Backup Reporter services are stopped automatically. After you successfully upgrade to Symantec OpsCenter Agent, you must manually uninstall Veritas Backup Reporter Agent.

6 7 8

Click Next to continue. Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter Agent installation. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space. Click Next.

The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

10 Click Install.
The installer starts installation of Symantec OpsCenter Agent 7.1.

11 After successful installation, you can view the installation logs or open the
readme file.

12 Click Finish.

160

Installing Symantec OpsCenter 7.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

1 2

On the OpsCenter View Builder host, insert the appropriate OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

3 4 5

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing Veritas Backup Reporter View Builder and shows the following message on the Welcome page:
The Installation has detected that the following software is already installed on your system. Veritas Backup Reporter: <version> It is recommended that you upgrade to Symantec OpsCenter View Builder 7.1 from VBR 6.6.1 or a higher version

Click Next to continue.

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

161

8 9

Select a new location and click Next. The installer shows a summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

10 Click Install.
The installer starts installation of Symantec OpsCenter View Builder 7.1.

11 After successful installation, you can view the installation logs or open the
readme file.

12 Click Finish.

Upgrading from Veritas Backup Reporter to OpsCenter 7.1 on UNIX

Use the following procedure to upgrade from Veritas Backup Reporter Server and Agent to Symantec OpsCenter Server and Agent respectively. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started.

Upgrading from Veritas Backup Reporter to OpsCenter Server 7.1 on UNIX

Use the following procedure to upgrade from Veritas Backup Reporter Server to Symantec OpsCenter Server on UNIX. To upgrade from VBR Server to OpsCenter Server 7.1 on UNIX

1 2 3

Open a UNIX console and log on as root on the target host. Mount the appropriate OpsCenter DVD on the computer that you want to upgrade to OpsCenter 7.1. Type the following command: ./install. Press Enter. If you are installing OpsCenter on Solaris Sparc, select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

The Welcome message is displayed. Press Enter to continue.

162

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

The installer then checks for an existing VBR installation. It displays the following message when VBR is installed:
Veritas Backup Reporter (VBR) <version> is installed on <hostname>. Do you want to upgrade from VBR <version> to Symantec OpsCenter [y,n,q] y

To upgrade to Symantec OpsCenter, type y and then press Enter. Note: In case you try to upgrade from an unsupported VBR version like 6.6 to OpsCenter 7.1, the installer displays the following message: Veritas Backup Reporter (VBR) 6.6 is installed on <host>. It is recommended that you upgrade to Symantec OpsCenter 7.1 from VBR 6.6.1 or a higher version. Do you want to upgrade from VBR 6.6 to Symantec OpsCenter 7.1? [y,n,q] (n)

The following message is displayed:

The existing VBR database and configuration files must be backed up before upgrading to Symantec OpsCenter. Where should the VBR database and configuration files be backed up? An OpsCenter_save directory will be created within the directory that you specify to store these files. (/var/symantec)

Type the directory name in which you want to save the VBR database and configuration files and then press Enter. To save the VBR database and configuration files in the default directory path (/var/symantec), press Enter only.

The installer displays a list of components that get installed like PBX, AT, OpsCenter Server, OpsCenter GUI etc. Review this list and press Enter to continue. The installer prompts for the following information:
Where do you want to install Symantec OpsCenter? (/opt)

Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

163

Review the installation directory path that you provided. Type y to confirm the installation directory path and press Enter. If any older version of packages like VRTSpbx is detected, it is automatically uninstalled and the required version is installed.

10 OpsCenter server is installed on the system.

The installer prompts for the following information:
Specify a location for the Symantec OpsCenter database. A directory named 'OpsCenterServer' will be created within the directory that you specify. (/var/symantec/)

Type a directory path under which to install the OpsCenter database and press Enter. The script creates the folder OpsCenterServer below the directory that you specify. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. In case the database installation directory (/var/symantec) does not exist on the host, the following information is displayed:
Directory "/var/symantec" does not exist. Do you want to create the directory? [y,n,q] y

Type y to confirm and press Enter. The following information is displayed:

The OpsCenter database server may require up to 1 GB of temporary space at runtime. By default, temporary files will be created in the database installation directory,/var/Symantec/OpsCenterServer

164

Installing Symantec OpsCenter 7.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,n,q] (n)

Type y and press Enter to specify an alternate directory for the database server temporary space. Specify the directory location when prompted. To use the database installation directory for database server temporary space, press Enter without typing a directory path. Review the installation options that you selected (database and database temp directory locations). Type y and then press Enter.

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. Specify a port number on which the old database can be started (13799)

Type a port number on which the old VBR database can be started and press Enter. To accept the default port number (13799), press Enter only. Note: Ensure that the port number that you enter is free and not used by any application.

13 You are prompted with the following message:

An older license key has been detected. Press <Return> to use the existing key. Do you want to enter a new key?<Enter one key at a time if there are multiple keys:

To use a new key, type the license key and press Enter. To use the existing key, press Enter only.

14 All the OpsCenter processes are started. The VBR processes are stopped after
OpsCenter Server is installed. Information is available on how to configure and restart VBR. See Restarting VBR after upgrading to OpsCenter 7.1 Server on page 165. If you uninstall Veritas Backup Reporter (VBR) from the OpsCenter host, the OpsCenter Server processes must be restarted after the VBR uninstallation is complete.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

165

See Uninstalling VBR server from the OpsCenter host on page 165. The following information is also displayed:

Web URL to access OpsCenter console. Location of install log, summary, and response files. Link on the OpsCenter logon page from where you can access the data migration status 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.1. You can also access the data migration status from the OpsCenter console. See Monitoring data migration from VBR to Symantec OpsCenter Analytics 7.1 on page 186.

Restarting VBR after upgrading to OpsCenter 7.1 Server

After you upgrade from VBR to OpsCenter 7.1 on Solaris, the VBR processes are stopped. In case you still want to use VBR after upgrading to OpsCenter 7.1, perform the following procedure to start VBR. To restart VBR after upgrading to OpsCenter 7.1 on Solaris

Navigate to the following directory:

cd /etc/init.d/

Run the following commands to restore the VBR server processes:

mv vbrserver_VBR vbrserver mv vbrweb_VBR vbrweb

Navigate to the following directory:

cd /opt/VRTSccsvs/bin/

Run the following command to restart all VBR processes.

./vbrserver start

Run the following command to check the status of VBR processes:

./vbrserver status

Uninstalling VBR server from the OpsCenter host

If you uninstall Veritas Backup Reporter (VBR) from the OpsCenter host, the OpsCenter Server processes must be restarted. This must be done after the VBR uninstallation is complete.

166

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

To uninstall VBR server from OpsCenter 7.1 host

1 2

Uninstall the VBR server software. See the product documentation for more information. Run the following command to restart all OpsCenter Server processes:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent 7.1 on UNIX
Use the following procedure to upgrade a VBR Agent to an OpsCenter Agent on UNIX. You do not require an OpsCenter Agent to collect data from NetBackup 7.1 or PureDisk. However, you must install OpsCenter Agent if you want to collect data from other backup products. Note: Once you upgrade your VBR Agent to the OpsCenter Agent, the port that the VBR Agent uses is not required in OpsCenter. The default port that the VBR Agent uses is 7806. To upgrade a VBR Agent to OpsCenter Agent on UNIX

1 2 3

Open a UNIX console and log on as root on the target host. Mount the appropriate OpsCenter DVD for the platform on which you are installing OpsCenter software. Type the following command:
./install.

Press Enter.

4 5

Select Agent from the displayed options (Server and Agent). Press Enter to install OpsCenter Agent. The Welcome message is displayed. Press Enter to continue.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

167

The following prompt is displayed:

Veritas Backup Reporter (VBR) <version> is installed on <host>. Do you want to upgrade from VBR <version> to Symantec OpsCenter Agent ? [y,n,q] (y)

To upgrade to Symantec OpsCenter, type y and then press Enter. Note: In case you try to upgrade from an unsupported VBR version like 6.6 to OpsCenter 7.1, the installer displays the following message: Veritas Backup Reporter (VBR) 6.6 is installed on <host>. It is recommended that you upgrade to Symantec OpsCenter Agent from VBR 6.6.1 or a higher version. Do you want to upgrade from VBR 6.6 to Symantec OpsCenter 7.1? [y,n,q] (n)

7 8

The installer displays a list of components that get installed like PBX, Symantec WebGUI Agent etc. Review this list and press Enter to continue. It is optional to configure OpsCenter Agent during installation. You may choose to configure OpsCenter Agent later either manually or by running /opt/VRTS/install/installOpsCenterAgent -configure command. The following prompt appears:
Are you ready to configure OPSCENTERAGENT? [y,n,q] (y)

To configure OpsCenterAgent now, type y and press Enter. Note: The installOpsCenterAgent script is also present in the Solaris_Sparc64/Agent directory of the DVD.

Enter the location where you want to install OpsCenter Agent. 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. To accept the default path (/opt), press Enter without typing a directory path.

168

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

10 Type y and then press Enter to confirm your installation options. 11 The OpsCenter Agent is installed. You can view the installation log files,
summary, and response files on the path mentioned.

Upgrade considerations
When you upgrade from Veritas Backup Reporter to OpsCenter 7.1 Server and access the OpsCenter console, you may not see data for some columns in the following views:
Monitor > Jobs No data is shown for Available Columns (columns that are not displayed) like PID, Owner, Parent, Data Movement etc. No data is shown in this view No data is shown for some columns No data is shown for some columns No data is shown for some columns No data is shown for some columns No data is shown for some columns

Monitor > Services Monitor > Policies Monitor > Media Monitor > Devices Manage > Storage Manage > Devices

This data is not shown because VBR does not collect this data and hence this data is not available in the VBR database. The data for all these columns is shown after data collection for the master server is enabled during data migration. Once the data collection is enabled, this data is collected from the master server and shown on the OpsCenter console. Note: For most of the entities like policies, media, devices etc., all previous data is also collected once data collection is enabled. However for jobs and image, previous data is not collected from the master server.

Troubleshooting database inconsistency issues during upgrade

The upgrade process may fail due to database inconsistency when you upgrade from VBR to OpsCenter server. Additional information may be displayed in the ServerService_<timestamp>.log file. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. For example, the log file may display the following message:

Installing Symantec OpsCenter 7.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, or removed columns or constraints from the VBR database tables. To resolve this issue, you must manually undo the modifications that you have made to the database so that the database schema is similar to the released version. To resolve database inconsistency errors

Modify the database as per the message in the ServerService_<timestamp>.log file. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. Copy the modified ccsvc.db and ccsvc.log files from VBR database to the following directory on the OpsCenter server: For Windows: <INSTALL_PATH>\server\db\upgrade\data For Solaris: <INSTALL_PATH>/SYMCOpsCenterServer/db/upgrade/data

Upgrade to OpsCenter server again. See Upgrading from Veritas Backup Reporter to OpsCenter Analytics 7.1 on Windows and UNIX on page 152.

Monitoring data migration from NOM to Symantec OpsCenter

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

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

172

Installing Symantec OpsCenter 7.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.5.4 and 6.5.6, the database is upgraded directly to the OpsCenter 7.1 database. The data migration from NOM 6.5.4 or 6.5.6 to the OpsCenter 7.1 database occurs in three stages. In the first stage, data that is specific to NOM is migrated to the OpsCenter database. The NOM data comprises of alerts, alert policies, users, domains, server groups etc. Note: You must create new alert policies in OpsCenter only after alert migration is complete. Table 2-11 gives details about the NOM data that is migrated and how it appears in OpsCenter. Table 2-11 NOM data migration Data in OpsCenter
Metadata about the managed master servers from NOM is migrated to OpsCenter. Once this data has been migrated to OpsCenter, you can view this data from Settings > Configuration > NetBackup page in the OpsCenter console.

NOM data that is migrated

Master server metadata

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. A normal NOM user is the Administrator in OpsCenter. A read-only NOM user is the Operator in 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. Users of other NOM domains can continue using their respective domains in OpsCenter. Once this data has been migrated to OpsCenter, you can view this data from the Settings > Users page in the OpsCenter console. Email and trap recipients All recipients and recipient groups are migrated from NOM to OpsCenter. Once the recipients have been migrated to OpsCenter, you can view this data from the Settings > Recipients page (both Email and SNMP subtabs) in the OpsCenter console.

Note: Recipient groups are not supported

in OpsCenter. Even though recipient groups are migrated to the OpsCenter database, the OpsCenter console does not display recipient groups.

174

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Table 2-11

NOM data migration (continued) Data in OpsCenter

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

NOM data that is migrated

Public and Private Groups

Installing Symantec OpsCenter 7.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

176

Installing Symantec OpsCenter 7.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 Table 2-10 User-created private and public composite reports in NOM are migrated as dashboard reports. Once these reports have been migrated, you can view the private composite reports from Reports > My Dashboard in the OpsCenter console. However, the user created public reports are not available for viewing. User-created reports in NOM (both Public and Private) are migrated as custom SQL queries. If you edit these reports in OpsCenter, you can directly edit SQL queries for these reports.

NOM data that is migrated

Note: To edit custom SQL reports in

OpsCenter, you must have a licensed version of OpsCenter (OpsCenter Analytics). All private graphical reports in NOM become tabular in OpsCenter. The concept of saving a report in NOM is different than OpsCenter. User must provide values for all the filters like Client Name, Policy Name etc. before you save a report in OpsCenter. In NOM, a user provides values for filters while running a report. Hence after migration is complete, these reports get default values for filters in OpsCenter. For example if you migrate a Skipped Files details for client report for a specific client like nom-ut6 from NOM, then in OpsCenter the report is configured to run on all the clients (instead of only nom-ut6). The WHERE clause of the OpsCenter SQL query has "IS NOT NULL" value. If there are special characters in a report name like (/ \ * ? | "), these special characters are replaced with an underscore '_' when you upgrade to OpsCenter 7.1. For example a

Installing Symantec OpsCenter 7.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.1. Shortcuts to reports are not migrated. Shortcuts to reports are not supported in OpsCenter. You need to manually configure My Portal again using OpsCenter reports.

NOM data that is migrated

Alert Policies and alerts

All alert policies and alerts are migrated from NOM to OpsCenter. You must create new alert policies in OpsCenter only after alert migration is complete. To see if alert policies have been migrated, see the Data Migration Status page.

After the NOM data has been migrated, the second stage of data migration begins. Note that in the second stage of data migration, data is migrated per master server. In the second stage, the following data is migrated for each master server:

Media server Client Storage Unit Volume group Volume Pool Robot Drives Services Catalog License Storage Service FSM DSM

178

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

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

179

Report Schedules

The concept of report schedules is different in NOM and OpsCenter. While creating schedule for a report in OpsCenter, you only need to specify the schedule details like time etc. However when you create a schedule in NOM, you provide the schedule details as well as filter values. The following steps are performed in the specified sequence to migrate scheduled reports from NOM to OpsCenter: The schedule is saved separately in the OpsCenter database The report filter values are inserted in the report definition The report is saved again.

In case a standard report is scheduled in NOM, the report is first saved under Reports > My Reports and then the schedule is attached to it. For example, if a standard report like Available Media is scheduled in NOM, then the standard report is saved in OpsCenter under Reports>MyReports view and the schedule is then attached to this report.

Note: Reports that come with NOM and are

composite reports (containing more than one report). Schedules for composite reports are not migrated. Example, Full Media Capacity, Restore Job Summary etc.

You can work in the OpsCenter console while this data is migrated in the background. Note: All NOM user preferences like column settings, SORD value etc. are not migrated to OpsCenter.

What happens when data migration is interrupted

Data migration can be interrupted due to many reasons, like network issues, stopping services on the OpsCenter server etc. For NOM 6.5.4 and 6.5.6, the database is upgraded directly to the OpsCenter7.1 database.

180

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

The data migration process can be interrupted when upgrade from NOM 6.5.4 or 6.5.6 database to the OpsCenter 7.1 database is in progress. Table 2-12 explains what happens when data migration is interrupted. Table 2-12 Scenario
Data migration is interrupted when data is migrated from NOM 6.5.4 and 6.5.6 to the OpsCenter 7.1 database.

What happens when data migration is interrupted Migration status

In this case, data migration resumes from the last checkpoint automatically. The data that had already been migrated does not need to be migrated again.

Note: The data migration for the following

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

Viewing the data migration status

You can also view the data migration status using the OpsCenter console. To view the data migration status

Access the data migration status page by doing any of the following:

In the Web browser address bar, enter the following: http://<host.domain>/opscenter/dbUpgradeStatus.do <host.domain> is the FQDN (Fully Qualified Domain Name) or IP address of the OpsCenter Server host. Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run
INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status

on UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then use http://<server-host>:8181/opscenter/dbUpgradeStatus.do. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus.do after the URL to access the data migration page at any point in time.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

181

On the OpsCenter logon page, use the Click here to see migration status link as shown in the following figure. The link is located at the bottom of the logon page on the right-hand side. This link is also located at the bottom of all OpsCenter console pages on the left-hand side. This link automatically disappears when the data migration is complete.

The data migration status is displayed as shown in the following figure:

182

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

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

Total Records

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

183

Migrated Records

Number of records of an entity that have been migrated to Symantec OpsCenter, as of now

Note: Migrated records are the number of

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

Click the Master Server Entity Migration Status tab to view the details of entities that are migrated per master server. This is shown in the following figure:

184

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

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

185

Status

The migration status for the respective master server. The following migration status is possible for a master server: Not Started: Data Migration has not started for this master server In Progress:: Entities for this master server are being migrated from NOM to OpsCenter Last 30 Days Jobs Migrated: This means that the second stage of data migration is complete for the specific master server. This status indicates that entities like policies, media, and jobs for the last 30 days have been migrated to OpsCenter and data collection in OpsCenter has been enabled for the selected master server. Because data collection has been enabled, the OpsCenter server starts collecting fresh data from the specific master server. You can start using the Monitor and Manage views of the OpsCenter console at this point.

Note: If data collection for a master server

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

186

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Migrated Records

Number of records for each master server that have been migrated to Symantec OpsCenter, as of now

Note: Migrated records are the number of

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

Monitoring data migration from VBR to Symantec OpsCenter Analytics 7.1

When you upgrade from VBR to OpsCenter Analytics, the OpsCenter Installation Wizard automatically detects an older VBR installation. The OpsCenter installer only stops the existing VBR services. It does not uninstall your existing VBR installation. You can manually uninstall VBR after successfully migrating data and using Symantec OpsCenter for some time. However, do not uninstall VBR server after upgrading to OpsCenter server software on a Windows platform. Read the following TechAlert if you want to uninstall VBR on Windows: http://www.symantec.com/business/support/index?page=content&id=TECH126226

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

187

During upgrade, the OpsCenter server is installed and the older VBR database is saved and started. The data migration from the older VBR database to the new OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter server. The data migration process may take time depending on the amount of data that has to be migrated. The following sections describe the data migration process from VBR to OpsCenter Analytics.

About upgrading the VBR database to Symantec OpsCenter Analytics 7.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. For VBR 6.6.1 and 6.6.2, the database is upgraded directly to the OpsCenter 7.1 database. The data migration from VBR 6.6.1 or 6.6.2 to the OpsCenter 7.1 database occurs in the following stages:

First stage in which VBR metadata and backup data is migrated from VBR to the OpsCenter database. The VBR metadata comprises of data related to alert policies, users, domains, views, SMTP server, and data purge settings etc. The backup data consists of entities like policy, media, devices etc. For entities like jobs, media history, scheduled jobs, and images, data for the last 30 days is migrated in this stage. Second stage in which Symantec Enterprise Vault archive data and report data is migrated. Third stage in which backup data older than 30 days (for NetBackup, Backup Exec, PureDisk, TSM, EMC NetWorker) is migrated from VBR to OpsCenter for each master server.

Table 2-13 gives details about the VBR metadata that is migrated in the first stage and how it appears in OpsCenter.

188

Installing Symantec OpsCenter 7.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. Once this data has been migrated to OpsCenter, the NetBackup agents and NetBackup data collectors can be viewed from Settings > Configuration > NetBackup in the OpsCenter console. The agents and data collectors for all products other than NetBackup can be viewed from Settings > Configuration > Agents in the OpsCenter console.

VBR data that is migrated

Agent and Data Collectors

Objects

Data related to master servers, media servers, clients, file systems, and EV archive-related information like vault server , Exchange Server is migrated to OpsCenter.

Note: Only those master servers, media

servers, and clients that have job data are migrated to OpsCenter.

Installing Symantec OpsCenter 7.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. A read-only VBR Administrator is the Analyst in OpsCenter. A normal VBR user is the Reporter in OpsCenter.

VBR data that is migrated

User information and domains

The users on the cc_users@hostname domain can continue using the same domain in OpsCenter. Users of other domains can also continue using their respective domains.

Note: Only the VBR default user

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

Note: Recipient groups are not supported

in OpsCenter. Even though recipient groups are migrated to the OpsCenter database, the recipient groups are not displayed in the OpsCenter console. Views All views from VBR are migrated to OpsCenter as client-type views. Once this data has been migrated to OpsCenter, you can see these views in the View Pane of the OpsCenter console.

190

Installing Symantec OpsCenter 7.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. To see if alert policies have been migrated, see the Data Migration Status page. See Viewing the data migration status on page 195.

VBR data that is migrated

Alert Policies

Note: Alerts from VBR are not migrated to

OpsCenter.

After the VBR metadata is migrated, backup data (for NetBackup, Backup Exec, PureDisk, IBM TSM, EMC NetWorker) is migrated per master server. The following data is migrated as a part of backup data for each master server:

Policy Devices (tape libraries , Tape drives, Disk pools etc.) Data Classification Media Media History (Last 30 days) Jobs (Last 30 days) Scheduled jobs (Last 30 days) Images (Last 30 days)

Once all this data (including jobs data for the last 30 days) has been migrated to the OpsCenter database for each master server, data collection for each master server is enabled automatically. The status for the specific master server is shown as Last 30 Days Jobs Migrated on the Data Migration status page. At this point, fresh data collection from the master server begins and you can start using the Monitor,Manage, and Reports tabs of the OpsCenter console. Note: If data collection for a master server was disabled in VBR, then data collection for the specific master server remains disabled after upgrading to OpsCenter Analytics. In such a case, data collection is not enabled automatically after migration.

Installing Symantec OpsCenter 7.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. In the second stage of data migration, Symantec Enterprise Vault archive data is migrated followed by report data. The following data is migrated as Symantec Enterprise Vault archive data in the second stage:

Archive policy (migrated per site) Exchange server (migrated per site) Vault server (migrated per site) Retention category Provisioning Group Vault Store Vault partition Vault and Savesets

After the archive data migration is complete, report data is migrated in the second stage. Table 2-14 gives details about the report data that is migrated and how it appears in OpsCenter.

192

Installing Symantec OpsCenter 7.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

Installing Symantec OpsCenter 7.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, you can view the My Backup Reports folder under Private Reports tree. Earlier in VBR, the My Backup Reports folder was under My Saved Reports folder. Custom SQL and Stored Custom SQL reports are not migrated to Symantec OpsCenter. Custom chargeback reports that you have created in VBR are not migrated to OpsCenter. The following VBR reports are not migrated to OpsCenter:

VBR data that is migrated

Forecast - File Count Job Duration - Historical Job Duration - Distribution Master Server Count Active Job Count Skipped File Report Drive Throughput Success Rate vs. Amount Backed Up Success Rate vs. Client Count Success Rate vs. Job Count Success Rate vs. File Count File Factor - Historical File Factor - Ranking File Savings - Historical File Savings - Ranking Protected Files vs. 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 (/ \ * ? | "), these special characters are replaced with an underscore '_' when you upgrade to OpsCenter 7.1. For example a media**summary report in VBR is renamed

194

Installing Symantec OpsCenter 7.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.1.

VBR data that is migrated

Chargeback variables and formulas

All VBR chargeback variables and formulae are migrated to OpsCenter. Once this data has been migrated, the chargeback variables and formulae can be viewed from Settings > Chargeback view in the OpsCenter console.

Report schedules

All report schedules are migrated from VBR to OpsCenter.

After the second stage of data migration is complete, the third stage of data migration begins. In the third stage of data migration, the backup data that remains to be migrated in the first stage (data older than 30 days) is migrated for each master server. The following data is migrated in the third stage for each master server:

Media History (Older than 30 days) Disk Pool history (Older than 30 days) Jobs (Older than 30 days) Scheduled jobs (Older than 30 days) Images (Older than 30 days)

If you upgrade from VBR versions lower than 6.6 to OpsCenter Analytics, you need to configure the following after data migration is complete:

SMTP server settings. The VBR SMTP server settings are not migrated to OpsCenter.

What happens when data migration is interrupted

Data migration can be interrupted due to many reasons, like network issues, accidental shutdown of OpsCenter server, stopping services on the OpsCenter server etc. For VBR 6.6.1 and VBR 6.6.2, the database is upgraded directly to the OpsCenter 7.1 database. Table 2-12 explains the scenario and what happens when data migration is interrupted.

Installing Symantec OpsCenter 7.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, data migration resumes from being migrated from VBR 6.6.1 and VBR 6.6.2 the last checkpoint automatically. The data to the OpsCenter 7.1 database. that had already been migrated does not need to be migrated again.

Note: The data migration for the following

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

Viewing the data migration status

You can also view the data migration status using the OpsCenter console. To view the data migration status

Access the data migration status page by doing any of the following:

In the Web browser address bar, enter the following: http://<host.domain>/opscenter/dbUpgradeStatus.do <host.domain> is the FQDN (Fully Qualified Domain Name) or IP address of the OpsCenter Server host. Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run
INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status

on UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then use http://<host.domain>:8181/opscenter/dbUpgradeStatus.do to access the data migration page at any point in time. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus.do after the URL to access the data migration page at any point in time.

On the OpsCenter logon page, use the Click here to see migration status link as shown in the following figure. The link is located at the bottom of the logon page on the right-hand side. This link is also located at the bottom of all OpsCenter console pages. This link automatically disappears when the data migration is complete.

196

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

The data migration status is displayed as shown in the following figure:

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. The Entity Migration Status tab shows the following columns (along with the migration summary):
Entity Displays the name of the database entity, such as Alert Policy, Policy, Disk Pool, Jobs etc. that is being migrated to OpsCenter Analytics. The total number of records of an entity that need to be migrated from VBR to Symantec OpsCenter Analytics.

Total Records

198

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Migrated Records

Number of records of an entity that have been migrated to Symantec OpsCenter, as of now

Note: Migrated records are the number of

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

Click the Master Server Entity Migration Status tab to view the details of entities that are migrated for each master server. The following figure shows a sample view of the Master Server Entity Migration Status tab:

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

199

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

200

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Status

The migration status for the respective master server. The following migration status are possible for a master server: Not Started: The data migration process for the master server has not started. In Progress: Entities for this master server are being migrated from VBR to OpsCenter Analytics. Last 30 Days Jobs Migrated: This means that the first stage of data migration is complete for the specific master server. This status indicates that entities like policies, media, and jobs for the last 30 days have been migrated to OpsCenter Analytics and data collection in OpsCenter Analytics has been enabled for the selected master server. Because data collection has been enabled, the OpsCenter server starts collecting fresh data from the specific master server. You can start using the Monitor and Manage views of the OpsCenter Analytics console at this point.

Note: If data collection for a master server

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

Installing Symantec OpsCenter 7.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, as of now

Note: Migrated records are the number of

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

Upgrading to OpsCenter Server on a different Windows system

This section explains how you can 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. Note: Symantec recommends that you enable 8.3 file name creation before installing OpsCenter components. If 8.3 file name creation is disabled, enable it and restart the WIndows host before installing or upgrading to OpsCenter components.

202

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Note the following points before you upgrade from NOM or VBR to OpsCenter 7.1 Server software on a different Windows system:

Manual upgrades are supported only within the Windows family. For example, you can upgrade from Windows 2000 to Windows 2008 but you cannot upgrade from a Windows platform to Solaris 10. 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, you can upgrade from NOM running on Windows 2000 (32-bit) to OpsCenter 7.1 on Windows 2008 R2 (64-bit). However, manual upgrade from a 64-bit system to a 32-bit system is not supported.

Manual upgrade to OpsCenter 7.1 Server is supported from the following NOM versions:

NOM 6.5.4 NOM 6.5.6

Manual upgrade to OpsCenter 7.1 Server is supported from the following VBR versions:

VBR 6.6.1 VBR 6.6.2

Use the following procedure to upgrade to OpsCenter Server software on a different Windows system. The procedure basically involves the following steps:

Back up your NOM or VBR database and configuration files using DataBackupUtility.exe for the appropriate architecture on your old NOM or VBR server. See Backing up your data on the NOM or VBR server on page 207. Copy this data from the old server to the server where you plan to install OpsCenter Server. Install the OpsCenter Server software and restore the NOM or VBR data using the OpsCenter installer. See Upgrading to OpsCenter Server on the new system on page 208.

Installing Symantec OpsCenter 7.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. To back up the NOM or VBR database

1 2 3 4 5

Log on to the NOM or VBR server as Administrator. Insert the appropriate OpsCenter product DVD in the DVD drive. Go to the appropriate OpsCenter platform directory (like x64 or x86) and then the Server directory. Run DataBackupUtility.EXE. This utility backs up the NOM or VBR database and configuration files on this system. 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, type a backup location or browse for the appropriate location. After entering the backup location, review the available and required space that is displayed in the dialog box. Click Start Backup.

After backing up the NOM or VBR database, the installer displays the following message:
Backup completed successfully for <product>

Click OK. Once the backup is complete, the utility creates a folder called <product>_Backup in the location that you specified. For example, if you are backing up the VBR database, VBR_Backup folder is created.

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. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started.

204

Installing Symantec OpsCenter 7.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. Copy the backed up NOM or VBR data (<product>_Backup folder) from the older NOM or VBR server to this system. Insert the appropriate OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.

5 6 7

On the Symantec DVD Browser, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server 7.1. The Symantec OpsCenter Installation Wizard appears. Click Next.

8 9

Read the license agreement, check I accept the terms of the license agreement and click Next. The following options are displayed:
Install to this computer only Select this option to install OpsCenter Server on this host. Install a clustered OpsCenter Select this option to install OpsCenter Server on all Server selected nodes, in a clustered mode. You need to install OpsCenter Server manually on each node of the cluster. This option is enabled if you have Veritas Cluster Server (VCS) installed. See Clustering Symantec OpsCenter on Windows on page 237. See Clustering Symantec OpsCenter Server on Solaris on page 248.

Select Install to this computer only.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

205

10 On the Installation Choice section, click Custom.

Check Upgrade using a backed up VBR or NOM database on a different system. Click Next.

11 On the Manual Database Upgrade screen, specify a location where you have
saved the old NOM or VBR database. You can also click Browse to specify a location.

12 On the Upgrade Settings screen, enter a port number on which the old NOM
or VBR database can be started. The default port number is 13799. Click Next.

13 On the Customize Location screen, enter the following information:

Program destination folder Enter the path where OpsCenter Server can be installed. Enter the path where the OpsCenter database can be installed.

Database destination folder

Review the information in the Disk space requirements table at the bottom of the screen. Click Next.

14 On the License Keys screen, enter your demo or permanent key that you have
received with the purchase of OpsCenter 7.1 and click Add Key. See About Symantec OpsCenter Analytics license keys on page 82. Click Next.

15 Click Next. The installer shows the summary of the settings that you have
selected for installation. Check Save Summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location.

16 Click Install.
The installer installs OpsCenter Server software.

206

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

17 After successful installation, you can view the OpsCenter console or view
installation logs. Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter Server. You can also access the data migration status from the OpsCenter console. See Monitoring data migration from NOM to Symantec OpsCenter on page 169.

18 Click Finish.

Upgrading to OpsCenter Server on a different UNIX system

This section explains how you can upgrade from NOM or VBR to OpsCenter server software on a different UNIX system. An example scenario is when NOM or VBR is running on Solaris 8 and you require the same data with OpsCenter on Solaris 10. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. Note the following points before you upgrade from NOM or VBR to OpsCenter 7.1 Server software on a different UNIX system:

Manual upgrades are supported only within the UNIX family. For example, you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from a Windows platform to Solaris 10. Manual upgrades are supported only within a particular OS family. For example, you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from RHEL 4.0 to Solaris 10. Manual upgrade from NOM to OpsCenter server is supported from specific NOM platforms. Ensure that NOM is running on the following platforms:

Linux RHEL 4.0, 5.0, 64-bit Solaris SPARC 9.0, 10.0, 64-bit Solaris x86 10.0, 64-bit

For example, you can upgrade from NOM running on Solaris SPARC 9 (64-bit) to OpsCenter server running on Solaris SPARC 10 (64-bit).

Manual upgrade from VBR to OpsCenter Server is supported on Solaris platforms. For example, you can upgrade from VBR running on Solaris 8 to OpsCenter server running on Solaris 10.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

207

Use the following procedure to upgrade to OpsCenter server software on a different UNIX system. The procedure basically involves the following steps:

Back up your NOM or VBR database and configuration files using Backup.sh utility on your old NOM or VBR server. See Backing up your data on the NOM or VBR server on page 207. Copy this data from the old server to the server where you plan to install OpsCenter server. Install the OpsCenter server software and restore the NOM or VBR data using the OpsCenter installer. See Upgrading to OpsCenter Server on the new system on page 208.

Backing up your data on the NOM or VBR server

Use the following procedure to back up your database and configuration files on the NOM or VBR server. To back up the NOM or VBR database

1 2 3

Go to the NOM or VBR server and log on as root. Mount the OpsCenter product DVD on the computer where you are installing OpsCenter software. Go to the appropriate OpsCenter platform directory and then the Server directory.

208

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

Run Backup.sh script. This script backs up the NOM or VBR database and configuration files on this system.
./Backup.sh

The script detects that you have NOM or VBR installed and prompts you for the backup location:
You have <product> installed. Please specify the backup location. A directory named OpsCenter_save will be created within to store the data [var/symantec]:

To back up the <product> data in a specific location, type a backup location and press Enter. To back up the <product> data in the default directory (/var/symantec), press Enter. A directory that is named OpsCenter_save is created in the backup location that you specify.

Upgrading to OpsCenter Server on the new system

Use the following procedure to install OpsCenter server and restore the old VBR or NOM data on the new system. To upgrade to OpsCenter Server on the new system

1 2 3 4

Log on as root on the server where you want to install OpsCenter. Copy the backed up NOM or VBR data (OpsCenter_save folder) from the older NOM or VBR server to this server. Mount the OpsCenter product DVD where you want are installing OpsCenter Server. Type the following command: ./install. Press Enter. If you are installing OpsCenter on Solaris Sparc, select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

5 6

The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter is already installed. The installer also examines the system for existing packages.

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX

209

The installer displays a list of components that get installed like PBX, AT, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue. The installer prompts you with the following question:
Where do you want to install Symantec OpsCenter? </opt>

Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.

Type y to confirm the directory path and press Enter.

10 OpsCenter Server is installed on the system.

The installer prompts for the following information:
Specify a location for the Symantec OpsCenter database. A directory named 'OpsCenterServer' will be created within the directory that you specify. (/var/symantec/)

Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory, the script creates the folder OpsCenterServer below your directory. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. In case the database installation directory (/var/symantec) does not exist on the host, the following information is displayed:
Directory "/var/symantec" does not exist. Do you want to create the directory? [y,n,q] y

Type y to confirm and press Enter. The following information is displayed:

The OpsCenter database server may require up to 1 GB of temporary space at runtime. By default, temporary files will be created in the database installation directory /var/Symantec/OpsCenterServer

210

Installing Symantec OpsCenter 7.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,n,q] (n)

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

12 Review the installation options you selected. The location of database directory
and the database temp directory is also displayed.

13 Type y and press Enter to confirm the selection and continue.

Type n and press Enter to repeat the configuration steps and revise your selection.

14 Once the configuration changes are completed, you are prompted with the
following question:
Do you want to restore data that has been backed up manually [y,n,q] <n>

Type y and then press Enter.

15 You are prompted for the location of the backed up directory:

Please specify the directory that contains the backed up data. <var/symantec>

Specify the location where you have copied the backed up data and press Enter.

Installing Symantec OpsCenter 7.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. Specify a port number on which the old database can be started <13799>

To start the old database on port 13799, press Enter. Otherwise enter any other port that is available and press Enter.

17 You are prompted for license information. Depending on whether older license
keys are detected or not, 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. If you do not enter a key, you get an unlicensed version. With the unlicensed version, you cannot access the licensed features. See About Symantec OpsCenter Analytics license keys on page 82. You can also add the license keys later from the OpsCenter console. See About managing licenses on page 307.

Post-installation tasks
The following sections explain how to start using OpsCenter and includes some performance tuning tips for OpsCenter.

Verifying that Symantec OpsCenter is running properly

After installing Symantec OpsCenter on either Windows or UNIX, perform a check to verify that OpsCenter is running properly.

212

Installing Symantec OpsCenter 7.1 Post-installation tasks

To verify that OpsCenter is running properly

Use the URL that is presented at the end of the OpsCenter Server installation to access the OpsCenter console. Alternately type the following in the Web browser address bar: http://<server-host>/opscenter Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run
INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status

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

UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then use http://<host.domain>:8181/opscenter. If the OpsCenter logon screen appears, the OpsCenter Server, the Web server, and the authentication service are running. The first time you log in, it takes longer than usual time for the GUI to load.

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, you are ready to start using the OpsCenter console. Table 2-16 lists the common tasks in OpsCenter and contains links to the corresponding topics and descriptions. 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, and provides solutions to possible issues. For administrator initial logon, the user name is admin and the password is password if you have chosen to keep the default password during installation. After initial logon, it is recommended that you change the user name and password.

To access and log on to the See About accessing the OpsCenter console. OpsCenter console on page 41.

To change the password for the administrator logon.

See Changing your OpsCenter password on page 307.

Installing Symantec OpsCenter 7.1 Post-installation tasks

213

Table 2-16 Task

To learn about the OpsCenter console components.

Links to get you started with OpsCenter (continued) Topic Description

This topic provides an overview of the console components.

Topic
See About OpsCenter console components on page 58.

To learn more about using See About using the OpsCenter For instructions on understanding and using the the OpsCenter console. console on page 39. various OpsCenter monitoring, managing, reporting, and settings views and related tasks, use the OpsCenter online Help .

About the start-up tasks that OpsCenter performs

OpsCenter performs the following tasks when it starts for the first time. When OpsCenter starts, it performs the following tasks:

Creates and initializes the security domain that the authentication broker requires. If these security domains are present, OpsCenter uses them. The following domains namely OpsCenterUsers, OpsCenterServices, and NOM_MACHINES are created when OpsCenter server is installed. Creates the OpsCenter admin user in the OpsCenterUsers domain with the default password as 'password'.

Tuning OpsCenter for more performance

The following settings can be tuned to improve OpsCenter performance. 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. These can be used as guidelines and should not be used as 100% accurate benchmarks.

About adding master servers to OpsCenter

If you need to add multiple master servers to the OpsCenter console, Symantec recommends that you add five master servers at one time. For example, if you have 20 master servers to be added, then you should not add all of them at once. Symantec recommends that you add them in groups of five in the following manner - 5+5+5+5. Once you add the first five master servers, wait until the initial data collection for these master servers is complete. To view the data collection status for a master server, go to Settings > Configuration > NetBackup in the OpsCenter console and then click the Data Collection Status tab on the page. The data

214

Installing Symantec OpsCenter 7.1 Post-installation tasks

collection status for a master server can be viewed from the Collection Status column.

About using a Web browser to access OpsCenter

Symantec recommends that you use Mozilla Firefox to access the OpsCenter console. Performance testing indicates that Mozilla Firefox works 1.25 times faster than Microsoft Internet Explorer.

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 OpsCenter runs fastest on a Windows 64-bit platform as compared to other Windows or UNIX platforms. See About OpsCenter platform compatibility on page 86.

About bandwidth utilization

The following table lists the average bandwidth that is consumed when OpsCenter collects data from a master server. Average Bandwidth used by OpsCenter Number of jobs per day
4.67 Kbps 10.381 Kbps 2500 More than 10,000

Note: The system that was used for testing was a NetBackup 7.1 master server running Windows 2003 on a Xeon-64 processor that has 2 GB RAM and 1.0 GbE LAN connection.

About performance tuning guidelines

You may want to tune OpsCenter to obtain incremental performance gains. This section describes important tuning parameters and settings that can result in improved performance. 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. See Moving the OpsCenter database to a different hard disk on page 215.

Installing Symantec OpsCenter 7.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. This should be done only if the logging level is greater than 1. See Saving the OpsCenter log files on a different drive on page 217. Symantec recommends that you defragment the OpsCenter database periodically. You must perform defragmentation once in a month. See About OpsCenter database defragmentation on page 270. Increase the heap size of the OpsCenter Server in accordance with the RAM. See Adjusting the heap size for OpsCenter components on page 221. Increase the database cache size in accordance with the RAM and database size. See Adjusting the OpsCenter database cache size on page 226. Create report schedules such that the email or export happens in system idle time when OpsCenter is not accessed frequently. Purge the OpsCenter data periodically. See About purging data periodically on page 227.

Moving the OpsCenter database to a different hard disk

Use the following procedure to move the OpsCenter database to a different hard disk. To move the OpsCenter database to a different hard disk on Windows

Stop all OpsCenter server services. Open the command line and enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

Open the databases.conf file with a text editor like notepad from the following directory: INSTALL_PATH\OpsCenter\server\db\conf This file has the following contents: "INSTALL_PATH\OpsCenter\server\db\data\vxpmdb.db" This path specifies the default location of the OpsCenter database.

216

Installing Symantec OpsCenter 7.1 Post-installation tasks

To move the database to a custom location like E:\Database, replace the contents of the file with the following: "E:\Database\vxpmdb.db" Make sure that you specify the path in double quotes. Also the directories in the specified path should not contain any special characters like %, ~, !, @, $, &, ^, # etc. For example, do not specify a path like E:\Database%. Save the databases.conf file.

Copy the database file to the new location. Copy vxpmdb.db and symcOpscache.db from INSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database. Restart all OpsCenter server services. To restart all OpsCenter services, enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete vxpmdb.db and symcOpscache.db from the default location (INSTALL_PATH\OpsCenter\server\db\data). To move the OpsCenter database to a different hard disk on UNIX

Stop all OpsCenter server processes. Enter the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

The default location of the OpsCenter database is /opt/SYMCOpsCenterServer/db/data. Back up the OpsCenter database (/opt/SYMCOpsCenterServer/db/data) to some other location. Enter the following command: cp R /opt/SYMCOpsCenterServer/db/data /backup/data

To move the database to a custom location like /usr/mydata, first create the new directory by entering the following command:
mkdir -p /usr/mydata

To move the database to a custom location like /usr/mydata,enter the following command:
mv /opt/SYMCOpsCenterServer/db/data/* /usr/mydata

Remove the symbolic link that exists for the OpsCenter database. Enter the following command:
unlink /opt/SYMCOpsCenterServer/db/data

Installing Symantec OpsCenter 7.1 Post-installation tasks

217

Create a symbolic link to /usr/mydata in /opt/SYMCOpsCenterServer/db/data. To create a symbolic link, enter the following command:
ln -s /opt/SYMCOpsCenterServer/db/data /usr/mydata

Restart all OpsCenter server processes by entering the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete vxpmdb.db and symcOpscache.db from /backup/data.

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. This should be done only if the debug level of logs is greater than 1. The default debug level of OpsCenter logs is 1. To know the debug level of your logs, see the following section. See Checking the debug level of logs on page 217. You can control how OpsCenter writes log files for OpsCenter Server, OpsCenter Agent, and the OpsCenter Web GUI components. See Saving the log files to a different directory on Windows on page 218. See Saving the log files to a different directory on UNIX on page 220.

Checking the debug level of logs

You can check the debug level of OpsCenter logs by using the following procedure.

218

Installing Symantec OpsCenter 7.1 Post-installation tasks

To check the debug level of logs

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

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. By default, 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

Installing Symantec OpsCenter 7.1 Post-installation tasks

219

To save the log files for OpsCenter server in a different location

Enter the following command to save log files to a different location:

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a p 58330 -o 148 -s LogDirectory="<New log directory location>"

Note: 58330 is the OpsCenter product ID. 148 is the OID for OpsCenter server.

2 3

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

To save the log files for OpsCenter Agent in a different location

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. 146 is the OID for OpsCenter Agent.

2 3

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

To save the log files for OpsCenter Web GUI in a different location

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. 147 is the OID for OpsCenter Web GUI.

2 3

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

220

Installing Symantec OpsCenter 7.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

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. 148 is the OID for OpsCenter server.

Enter the following command to stop the OpsCenter server process:

/opt/SYMCOpsCenterServer/bin/stopserver

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

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. 146 is the OID for OpsCenter Agent.

Enter the following command to stop the OpsCenter Agent process:

/opt/SYMCOpsCenterAgent/bin/stopagent

Enter the following command to start the OpsCenter server process:

/opt/SYMCOpsCenterAgent/bin/startagent

Installing Symantec OpsCenter 7.1 Post-installation tasks

221

To save the log files for OpsCenter Web GUI in a different location

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. 147 is the OID for OpsCenter Web GUI.

Enter the following command to stop the OpsCenter Web server process:
/opt/SYMCOpsCenterServer/bin/stopgui.sh

Enter the following command to start the OpsCenter Web server process:
/opt/SYMCOpsCenterServer/bin/startgui.sh

Adjusting the heap size for OpsCenter components

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

Adjusting the default heap size for the OpsCenter server

If the OpsCenter server processes are consuming a lot of memory (which may happen with large OpsCenter configurations), it may be helpful to increase the OpsCenter Server heap size. The OpsCenter Server default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Server 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.

222

Installing Symantec OpsCenter 7.1 Post-installation tasks

To adjust the heap size on Windows servers

Open OpsCenterServerService.xml file from the following location on the OpsCenter server:
INSTALL_PATH\OpsCenter\server\bin

Modify the Xmx1024M value in the following string.

<CmdArg value="-Xms512M -Xmx1024M

For example, replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB. On 64-bit systems, modify the -Xmx2048M value in the following string:
<CmdArg value="-Xrs -Xmx2048M

For example, replace -Xmx2048 with -Xmx4096 to increase the maximum heap size from 2048 MB to 4096 MB.

3 4

Save the OpsCenterServerService.xml file. You must restart all OpsCenter server services for the changes to be effective. Enter the following commands to first stop and then start all OpsCenter server services as follows:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

To adjust the heap size on UNIX servers

Open startserver file from the following location:

/opt/SYMCOpsCenterServer/bin

Modify the -Xmx2048M value in the following string:

MAX_HEAP=-Xmx2048M

For example, replace -Xmx2048M with -Xmx4096M to increase the maximum heap size from 2048 MB to 4096 MB.

Installing Symantec OpsCenter 7.1 Post-installation tasks

223

3 4

Save the startserver file. You must restart all OpsCenter server processes for the changes to be effective. Enter the following commands to first stop and then start all OpsCenter server processes as follows:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Adjusting the default heap size for the Symantec OpsCenter Web server
The OpsCenter Web server default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Web server default heap size can be increased from 1024 MB to a higher value (like 2048 MB) for 64-bit platforms. You can determine a higher value based on the physical (RAM) and virtual memory that is available on your system. Note: If you start seeing poor performance in the OpsCenter console every few days and restarting the Symantec OpsCenter Web server service fixes the problem, you should increase the Web server default. To adjust the heap size on Windows servers

Open OpsCenterGUIService.xml file from the following location on the OpsCenter server:
INSTALL_PATH\OpsCenter\gui\bin\OpsCenterGUIService.xml

Modify the Xmx1024m value in the following string.

<EnvVar name="JAVA_OPTS" value="-Xrs -Xms512m -Xmx1024m

For example, replace -Xmx1024m with -Xmx1400m to increase the maximum heap size from 1024 MB to 1400 MB. Note: This string may be listed twice in the OpsCenterGUIService.xml file. You can change the first occurrence of -Xmx1024m in the OpsCenterGUIService.xml file to adjust the heap size.

224

Installing Symantec OpsCenter 7.1 Post-installation tasks

3 4

Save the OpsCenterGUIService.xml file. You must restart all OpsCenter server services for the changes to be effective. Enter the following commands to first stop and then start all OpsCenter server services as follows:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

To adjust the heap size on UNIX servers

Open startGUI file from the following location:

/opt/SYMCOpsCenterGUI/bin

Modify the Xmx1024M value in the following string.

JAVA_OPTS="-Xrs -d64 -Xms512M -Xmx1024m...

For example, replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB.

3 4

Save the startGUI file. You must restart all OpsCenter server processes for the changes to be effective. Enter the following commands to first stop and then start all OpsCenter server processes as follows:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Adjusting the default heap size for the OpsCenter Agent

If the OpsCenter Agent processes are consuming a lot of memory (which may happen with large OpsCenter configurations), it may be helpful to increase the OpsCenter Agent heap size. The OpsCenter Agent default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Agent default heap size can be increased from 1024 MB to a higher value (like 2048 MB) for 64-bit platforms. You can determine a higher value based on the physical (RAM) and virtual memory that is available on your system. Note: The OpsCenter Agent runs as a 32-bit application on 64-bit Windows platforms. Hence, the OpsCenter Agent default heap size can be increased from 1024 MB up to 1400 MB for Windows 64-bit platforms.

Installing Symantec OpsCenter 7.1 Post-installation tasks

225

To adjust the heap size on Windows servers

Open OpsCenterAgentService.xml file from the following location on the OpsCenter server:
INSTALL_PATH\OpsCenter\Agent\bin

Modify the Xmx1024M value in the following string.

<CmdArg value="-Xms512M -Xmx1024M

For example, replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB.

3 4

Save the OpsCenterAgentService.xml file. You must restart the OpsCenter Agent service for the changes to be effective. To restart the OpsCenter Agent service, first stop and then start the Symantec OpsCenter Agent Service. Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Agent Service.

Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Agent Service.

To adjust the heap size on UNIX servers

Open startagent file from the following location:

/opt/SYMCOpsCenterAgent/bin

Modify the Xmx1024M value in the following string.

MAX_HEAP=-Xmx1024M

For example, replace -Xmx1024M with -Xmx2048M to increase the maximum heap size from 1024 MB to 2048 MB.

3 4

Save the startagent file. You must restart the OpsCenter Agent process for the changes to be effective. Enter the following commands to first stop and then start OpsCenter Agent process as follows:
/opt/SYMCOpsCenterAgent/bin/stopagent /opt/SYMCOpsCenterAgent/bin/startagent

226

Installing Symantec OpsCenter 7.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. After you install OpsCenter, the database size can grow rapidly as you add more master servers. Sybase automatically adjusts the cache size for optimum performance. You can also set the cache size using the -c server option. To set the cache size using the -c server option on Windows servers

Open the install_path\OpsCenter\server\db\conf\server.conf file. For example, to increase the cache size to 512 MB, add -c 512M -cs to the content of server.conf file:
-n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786) -o "install_path\db\log\server.log" -m

should be changed to
-n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786) -o "install_path\db\log\server.log " -c 512M -cs -m

The -cs option logs the cache size changes for the database server. In the same manner, to increase the cache size to 1 GB, you should add -c 1G -cs to the content of the server.conf file.

Stop and restart the OpsCenter services, as follows:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

Installing Symantec OpsCenter 7.1 Post-installation tasks

227

To set the cache size using the -c server option on UNIX servers

Open the /opt/SYMCOpsCenterServer/db/conf/server.conffile and change the value of the -c option. For example, you can increase the Sybase cache size to 512 MB by changing the server.conf file content. The following:
-n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786;) -gp 8192 -ct+ -gd DBA -gk DBA -gl DBA -ti 60 -c 25M -ch 500M -cl 25M -ud -m

should be changed to:

-n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786;) -gp 8192 -ct+ -gd DBA -gk DBA -gl DBA -ti 60 -c 512M -cs -ud -m

This example replaced -c 25M -ch 500M -cl 25M with -c 512M -cs in the server.conf file to increase the cache size to 512 MB. In the same manner, to increase the cache size to 1 GB, replace -c 25M -ch 500M -cl 25M with -c 1G -cs. The -ch and -cl server options are used to set the maximum and the minimum cache size respectively. The -cs option logs the cache size changes for the database server.

2 3

Save the server.conf file. Stop and restart the OpsCenter processes, as follows:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh start

About purging data periodically

You should purge the OpsCenter data periodically. See Configuring the data purge period on the OpsCenter Server on page 309. The OpsCenter database should be defragmented after a purge operation. See Defragmenting the OpsCenter database on page 271.

228

Installing Symantec OpsCenter 7.1 Post-installation tasks

About OpsCenter performance and floating-point calculations

Symantec OpsCenter performs certain calculations that require floating-point math. If the server's processor does not have a dedicated floating-point unit, the calculations are handled in floating-point emulation. Emulation mode slows down OpsCenter's performance. Symantec does not recommend running OpsCenter on any server that lacks a dedicated floating-point unit. Performance issues exist when the OpsCenter server software is installed on a Sun T1 server. Symantec recommends that you install OpsCenter server software on a Sun T2 server. The issue of limited floating point capability on T1 servers has been resolved with the T2 servers.

About known performance issues

The following known issues may occur when the database size increases:

The performance of OpsCenter reports degrades. Reports are slow and take a longer time to run. If you have configured report schedules, the reports may reach later than the scheduled time. Procedure-based reports may not run before timeout happens (in 30 minutes). Symantec recommends that you schedule procedure-based reports in such a scenario. 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

Installing Symantec OpsCenter 7.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.1 server. When you upgrade from NOM or VBR to OpsCenter server, the OpsCenter installer only stops the existing NOM or VBR services. It does not uninstall your existing NOM or VBR installation. If you have not uninstalled NOM or VBR, you can use your older installation. In case you have not uninstalled NOM or VBR and want to use your existing NOM or VBR software, use the following procedure. To start using NOM or VBR on Windows

1 2

Log on to the OpsCenter server as an Administrator. Uninstall OpsCenter server software. See Uninstalling Symantec OpsCenter 7.1 on Windows on page 231.

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.

230

Installing Symantec OpsCenter 7.1 Uninstalling Symantec OpsCenter on Windows and UNIX

Start all NOM or VBR services by entering the following command:

NOM <INSTALL_PATH>\NetBackup Operations Manager\bin\admincmd\NOMAdmin -start_service <INSTALL_PATH>\Tools\cscript vx_services_start.vbs

VBR

Log on to the NOM or VBR console.

In case domains are not visible on the login page and you cannot log on to NOM, you must reinstall Symantec Product Authentication Service that was shipped with your NOM version. See the NOM documentation for more information. To start using NOM or VBR on UNIX

1 2

Log on to the OpsCenter server as root. Uninstall OpsCenter server software. See Uninstalling Symantec OpsCenter 7.1 on UNIX on page 231.

Enter the following command to start all NOM or VBR processes:

NOM VBR /<INSTALL_PATH>/VRTSnom/bin/NOMAdmin -start_service /<INSTALL_PATH>/VRTSccsvs/bin/vbrserver start

Log on to the NOM or VBR console.

In case domains are not visible on the logon page and you cannot log on to NOM, you must reinstall Symantec Product Authentication Service that was shipped with your NOM version. See the NOM documentation for more information.

Uninstalling Symantec OpsCenter on Windows and UNIX

This section describes uninstallation procedures for OpsCenter on Windows and UNIX. Note: After a rollback, the keys are not recreated to display an entry in Add or Remove Programs dialog box. If a rollback occurs during an uninstall of OpsCenter, the keys are not removed from Add or Remove Programs dialog box. You must remove OpsCenter. Use setup.exe to remove OpsCenter.

Installing Symantec OpsCenter 7.1 Uninstalling Symantec OpsCenter on Windows and UNIX

231

Uninstalling Symantec OpsCenter 7.1 on Windows

Use the Windows Add/Remove Programs utility to uninstall OpsCenter on a Windows host. Note: Before uninstalling OpsCenter components, ensure that NetBackup-Windows GUI is not running. Close any NetBackup-Windows GUI consoles that are open before uninstalling OpsCenter components. To uninstall Symantec OpsCenter Server on Windows

1 2 3

Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter Server and click Remove. For Windows 64-bit systems, click Symantec OpsCenter Server (64bit) and click Remove.

Click Next to continue and remove Symantec OpsCenter Server from your computer.

To uninstall Symantec OpsCenter Agent on Windows

1 2 3 4

Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter Agent and click Remove. Click Next to continue and remove Symantec OpsCenter Agent from your computer.

To uninstall Symantec OpsCenter View Builder on Windows

1 2 3 4

Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter View Builder and click Remove. Click Next to continue and remove Symantec OpsCenter View Builder from your computer.

Uninstalling Symantec OpsCenter 7.1 on UNIX

Use the Uninstall Script, which resides in the root directory of the product DVD and also in opt/VRTS/install directory, to uninstall OpsCenter on a UNIX host.

232

Installing Symantec OpsCenter 7.1 Uninstalling Symantec OpsCenter on Windows and UNIX

Note: If you want to reinstall OpsCenter components, use the product DVD. You cannot reinstall OpsCenter components using the install scripts in the opt/VRTS/install directory.

Note: Symantec recommends that you do not cancel or interrupt the uninstallation process once it is started. To uninstall OpsCenter Server on UNIX

1 2

Open a UNIX console and log on as root on the target host. Change to the following directory:
opt/VRTS/install

Type the following command and press Enter:

./uninstallOpsCenterServer

The Uninstall Script checks the components that are installed on the system. When you upgrade from VBR server to the OpsCenter Server and then uninstall OpsCenter Server, you may be prompted with the following question:
Do you want to uninstall package VRTSccsvs from <host name> which is dependent on package VRTSpbx? [y,n,q,?] (n)

If you see this prompt, type n and press Enter. The VBR uninstaller (and not the OpsCenter uninstaller) must be used to remove the VRTSccsvs package.

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

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

To uninstall OpsCenter Agent on UNIX

1 2

Open a UNIX console and log on as root on the target host. Change to the following directory:
/opt/VRTS/install

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

233

Type the following command and press Enter:

./uninstallOpsCenterAgent

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

When asked to confirm if you want to uninstall OpsCenter Agent, 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.

Clustering Symantec OpsCenter

The following sections describe how you can cluster OpsCenter 7.1.

About a Symantec OpsCenter cluster

Clusters provide high availability of applications and data to users. In a cluster, two or more nodes are linked in a network and work collectively as a single system. Each node can access the shared disks with the help of cluster software. All nodes in a cluster are constantly aware of the status of resources on the other nodes. If a node becomes unavailable, resources running on that node migrate to an available node. Symantec OpsCenter (OpsCenter) operates in an active or passive failover configuration. OpsCenter Server must be installed on the active node and the passive (or failover nodes). When a failover occurs in an OpsCenter cluster, OpsCenter is shut down on the active node and starts on one of the failover nodes in the cluster. During failover, users experience only a short interruption in service. This failover provides high availability for OpsCenter. You can cluster only the OpsCenter Server. Installing OpsCenter in a clustered environment makes OpsCenter a highly available application.

Supported OS and cluster solutions

An OpsCenter cluster is supported on Windows and Solaris platforms. You can install an OpsCenter 7.1 cluster on the following platforms:

Windows 2008 R2 x64

234

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

Windows 2008 x86 and x64 Windows 2003 x86 and x64 Solaris SPARC 10

For Symantec OpsCenter to be clustered, you must have Veritas Cluster Server (VCS) installed. Table 2-17 lists the supported versions of VCS. Table 2-17 Platform
VCS Windows VCS Solaris

OpsCenter cluster support matrix Latest supported version Start of support

5.1 5.1 4.2 RP2 4.3

VCS is a high-availability solution for cluster configurations. With VCS you can monitor systems and application services, and restart services on a different system when hardware or software fails. For more information about VCS, see the Veritas Cluster Server User's Guide. Note: Clustered OpsCenter is not supported on MSCS.

About running commands on the active node

For a clustered OpsCenter server, you must run commands on the active node. You may get unexpected results if you run a command on an inactive node. The command may fail to run and may sometimes result in an unexpected behavior. For example, running the dbbackup command on an inactive node may result in the following unexpected result: Command: E:\OpsCenter\server\bin>dbbackup.bat E:\temp Result: "Could not find Z:\OpsCenter\server\config\db.conf file" In addition, the OpsCenter service group may failover if the command requires restarting the OpsCenter services. Some OpsCenter commands or utilities like the support utility require restarting the services.

Installing Symantec OpsCenter 7.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. To check if AT and PBX are connected, verify whether pbxexchflag of the authentication service is set or not. When pbxexchflag is set, its value is equal to 1 and this means that PBX and AT are connected. Note: The information in this section applies to OpsCenter clusters only. Before setting the value of pbxexchflag, you must stop all OpsCenter Server services, Symantec Product Authentication Service and Symantec Private Branch Exchange. After setting the value of pbxexchflag to 1, you must restart these services. Use the following procedure to connect the authentication service and PBX components. To connect Symantec Product Authentication Service and Symantec Private Branch Exchange

Open the command prompt and enter the following command:

INSTALL_PATH\Security\Authentication\bin\vssat.exe showispbxexchflag

This command gives the value of pbxexchflag. If the value of pbxexchflag is 0, you need to set it to 1. In case the value of pbxexchflag is 1, you do not need to follow the remaining steps.

Navigate to INSTALL_PATH\Security\Authentication\bin directory. Enter the following command at the bin directory to set the value of pbxexchflag:
vssat.exe setispbxexchflag --enable

The value of pbxexchflag is set to 1. Verify if the value of pbxexchflag is 1. See step 1.

Stop all the OpsCenter Server services by executing the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

236

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

Stop Symantec Product Authentication Service by performing either of the following steps:

Use the stop option in the Windows Service pane, or Execute the following command in a command console:
net stop vrtsat

Restart Symantec Product Authentication Service by performing either of the following steps:

Use the start option in the Windows Service pane, or Execute the following command in a command console:
net start vrtsat

Restart all the OpsCenter Server services by performing the following steps:

Navigate to INSTALL_PATH\OpsCenter\server\bin directory. Restart all the OpsCenter Server services by executing the following command:
opsadmin.bat start

To connect Symantec Product Authentication Service and Symantec Private Branch Exchange on Solaris

Open the command console and enter the following command:

/opt/VRTSat/bin/vssat showispbxexchflag

This command gives the value of pbxexchflag. If the value of pbxexchflag is 0, you need to set it to 1. In case the value of pbxexchflag is 1, you do not need to follow the remaining steps of this procedure.

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.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

237

Stop all the OpsCenter Server services by entering the following command:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

Stop Symantec Product Authentication Service by issuing kill command on the process ID of the vxatd service. For example, if the process ID of vxatd service is 203, run the following command:
kill 203

Run the following command to restart Symantec Product Authentication Service:

/opt/VRTSat/bin/vxatd

Run the following command to restart all the OpsCenter Server services:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Clustering Symantec OpsCenter on Windows

This section provides information about installing Symantec OpsCenter in a clustered mode, on a Windows host. Table 2-18 provides the Windows clustering steps. 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. See Prerequisites for Symantec OpsCenter cluster on Windows on page 238. See Installing Symantec OpsCenter Agent 7.1 and AT on a remote Windows host on page 239.

Make sure that you have met all prerequisites.

Install OpsCenter 7.1.

Limitations of Symantec OpsCenter cluster on Windows

An OpsCenter cluster has the following limitations:

238

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

Only the OpsCenter Server can be clustered.OpsCenter Agent and the OpsCenter View Builder cannot be clustered. Upgrades from previous versions of NOM or VBR to clustered OpsCenter Server is not supported. Note that an OpsCenter 7.0 or 7.0.1 cluster can be upgraded to an OpsCenter 7.1 cluster. OpsCenter cluster cannot co-exist with any other Symantec product running in secure mode using the Symantec Product Authentication Service. OpsCenter does not support clustered AT.

Prerequisites for Symantec OpsCenter cluster on Windows

This section contains information about the requirements that must be met before you install and configure OpsCenter in a clustered mode, on a Windows host.

Verify that VCS and OpsCenter support your hardware. For a list of supported storage devices, visit the following Web site: http://entsupport.symantec.com Verify that the supported version of VCS is correctly installed and configured. Follow the steps in the Veritas Cluster Server Installation Guide. For VCS Windows 4.2 versions, ensure that the patch available through Technote 278307 is installed before installing OpsCenter. For OpsCenter, the supported VCS version starts from 4.2 RP2. The patch is available from the following URL: http://entsupport.symantec.com/docs/278307 This Technote is applicable to OpsCenter. Verify that no VCS resource group and resource exist with the same name as that which you intend to use for OpsCenter. The SharedDisk must be configured and accessible to all cluster nodes where you want to install OpsCenter. Verify that you have an IP address and host name (virtual host name) to be assigned to the OpsCenter resource in VCS. Only use these for the OpsCenter resource. The virtual host name must be the short name and less than 15 characters. Also, ping the IP address and verify that the IP address is not plumbed. Verify that you can mount the disk. Verify that you have the OpsCenter installation program and a valid license key.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

239

For a Windows cluster, verify that the cluster disk groups and dynamic volumes for OpsCenter are created on the shared storage. Refer to theVeritas Storage Foundation Administrators Guide for details. Verify that all VCS services are up and running on all the nodes in the cluster. Verify that OpsCenter installation is carried out with the domain admin account. Before installing OpsCenter Server, ensure that Symantec OpsCenter Agent 7.1 (PBX) and Symantec authentication service (AT) Server are installed separately on a remote host. PBX is installed when you install OpsCenter 7.1 Agent. Note the following points about installing OpsCenter Agent 7.1 (PBX) and AT on the remote host:

Symantec recommends that you first install OpsCenter Agent 7.1 (PBX) and then install AT from the OpsCenter 7.1 DVD. AT must be installed in a non-clustered mode. AT can be installed in Root + AB or AB mode on the remote host.

AT must be installed separately (and not along with OpsCenter) on the remote host. For more information about installing AT, see the Symanetc Infrastructure Core Services Installation Guide.

Verify that authentication service and PBX components on the remote host are connected. See Connecting Symantec Product Authentication Service and Symantec Private Branch Exchange on page 235.

Installing Symantec OpsCenter Agent 7.1 and AT on a remote Windows host

OpsCenter Server requires that OpsCenter Agent 7.1 (PBX) and Symantec Product Authentication Service (AT) are installed on a standalone host, before OpsCenter can be clustered. Symantec recommends that you first install OpsCenter Agent 7.1 and then install AT from the OpsCenter 7.1 DVD. You must install the version of AT Service that is shipped with OpsCenter 7.1. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode. Symantec recommends that you configure AT in a 'Root+AB' mode. Clustered OpsCenter Server uses this authentication broker. To establish a connection between AT host and OpsCenter Server host, you need to create a

240

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

principal user on the AT host. Use the credentials of this user when installing OpsCenter Server. Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server. You must upgrade to the version of authentication service that is shipped with OpsCenter 7.1.

Note: OpsCenter does not support clustered AT.

Note: In case of updates made to AT for OpsCenter 7.1, see the following technote for the latest information: http://entsupport.symantec.com/docs/336967 The OpsCenter Agent 7.1 and AT can be installed on the remote host using the following procedure. 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.1 and AT. Install OpsCenter Agent 7.1 on the remote host. See Installing Symantec OpsCenter Agent on Windows on page 109.

Install AT from the OpsCenter 7.1 DVD.

If autorun is enabled, the Symantec OpsCenter Installation Wizard appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec OpsCenter Installation Wizard appears.

4 5

On the Symantec OpsCenter Installation Wizard, click the Installation link. Click Symantec Product Authentication Service.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

241

Click Next. The VxSSVRTSatSetup.exe is executed. Note that you should not cluster the AT service, as OpsCenter does not support clustered AT. See Symantec Infrstructure Core Services Installation Guide for more information about the VxSSVRTSatSetup.exe.

Create a principal user on the AT host using the following command: AT_INSTALL_DIR/bin/vssat addprpl --prplname <principal name>
--password <principal name password> --pdrtype ab --domain broker --prpltype service --is_broker_admin --is_domain_admin

AT_INSTALL_DIR is the directory where AT is installed. The default location on 32-bit Windows platforms is: %Program
Files%\VERITAS\Security\Authentication

The default location on 64-bit Windows platforms is:

%ProgramFiles(x86)%\VERITAS\Secruity\Authentication

Installing OpsCenter Server 7.1 on a Windows cluster

To cluster OpsCenter and make it highly available, you must install and configure OpsCenter in a clustered mode. Note: To install OpsCenter Server in clustered mode, first install the OpsCenter Server on the active node and then on the passive nodes. Also, you need to install OpsCenter Server manually on all the nodes. To install OpsCenter Server in a clustered mode on Windows

1 2

On an active cluster node where you want to install OpsCenter server, insert the OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec OpsCenter Installation Wizard appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec OpsCenter Installation Wizard appears.

3 4 5

On the Symantec OpsCenter Installation Wizard, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. Click Next.

242

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

6 7

Read the license agreement, check I accept the terms of the license agreement and click Next. Select Install a clustered OpsCenter Server to install OpsCenter Server in clustered mode. You need to install OpsCenter Server manually on each node of the cluster. This option is enabled if you have Veritas Cluster Server (VCS) installed.

In the Installation Method section, click Typical to use the default settings and installation location. Also compare the space that is required for installation with the actual space available in the installation directory. Note: Click Custom if you want to change the default settings and locations. Click Next.

On the License Keys screen, enter the demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. Note: You can also add the license keys from the OpsCenter console. See About managing licenses on page 307. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. The license type information is also shown along with the key. More information about licenses is available. See About the OpsCenter licensing model on page 81.

10 Click Next. The Authentication Settings screen is displayed. 11 On the Authentication Settings screen, enter the following details of a
principal user to connect to the host where AT authentication broker (Root + AB or AB) is installed:

Authentication service host name Authentication service port number (2821 is the default port number) Authentication service user name Authentication service Password Authentication service Domain Name (broker is the default domain name)

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

243

Note: You must have this principal user created on the authentication broker (AB) host. See Installing Symantec OpsCenter Agent 7.1 and AT on a remote Windows host on page 239.

Note: Ignore this step if you are installing OpsCenter on a passive node.

12 Click Next. The Cluster Settings screen is displayed. 13 On the Cluster Settings screen, enter the following information:
Cluster Group Name Enter the name for the OpsCenter cluster. For example: OpsCenter_Server Enter the virtual host name that is assigned to the OpsCenter cluster. For example: Oc_cluster. The virtual host name must be the short name and less than 15 characters. Enter the IP address that assigned to the OpsCenter cluster Enter the subnet mask . For example: 255.255.252.0 Select the shared drive path that you have configured in VxVM. For example, Z:\ Select LAN as a public network. You can select different public network for passive nodes.

Virtual host Name

Virtual IP address

Subnet mask Path to Shared data

Public Network

Note: While installing OpsCenter on a passive node, only Public Network option is enabled.

14 Click Next. The installer shows the summary of the settings that you have
selected for OpsCenter Server installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

244

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

15 Click Install.
The installer starts installing the OpsCenter Server software. In a clustered mode, 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 on a Windows cluster and VCS is not configured properly, 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. The icon should actually be red for an installation failure. When you click Next, the correct red icon is shown.

16 After successful installation, you can view the OpsCenter console or view
installation logs.

17 Click Finish. Repeat this procedure for all the cluster nodes.
Note: After installing an OpsCenter cluster on Windows 2008 R2 x64 system, you need to manually bring the NetBackupOpsCenterVCS resource online. You can bring the NetBackupOpsCenterVCS resource online from the CLI or by using the cluster GUI. 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.0 (or 7.0.1) cluster to OpsCenter 7.1 cluster
Use the following procedure to upgrade from OpsCenter 7.0 (or 7.0.1) cluster to OpsCenter 7.1 cluster on Windows. Note: To upgrade to OpsCenter 7.1 Server in a clustered mode, first install the OpsCenter 7.1 Server on the active node and then on the passive nodes. Also, you need to install OpsCenter Server manually on all the nodes.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

245

To upgrade to OpsCenter 7.1 Server in a clustered mode on Windows

1 2

From the active node of the OpsCenter 7.0 (or 7.0.1) cluster that you want to upgrade, insert the OpsCenter DVD in the DVD drive.

If autorun is enabled, the Symantec OpsCenter Installation Wizard appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec OpsCenter Installation Wizard appears.

3 4 5 6

On the Symantec OpsCenter Installation Wizard, click the Installation link. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. Click Next. The Welcome Page of the Installation Wizard appears. The Installation Wizard detects an existing installation of OpsCenter Server 7.0 (or 7.0.1) on the system. Depending on the installed 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 Server: Version 7.0 In order to upgrade to a newer version, the existing Symantec OpsCenter Server will be removed. Click Next to continue.

7 8

Read the license agreement, check I accept the terms of the license agreement and click Next. Select Install a clustered OpsCenter Server to install OpsCenter Server in clustered mode. You need to install OpsCenter Server manually on each node of the cluster. This option is enabled if you have Veritas Cluster Server (VCS) installed.

In the Installation Method section, click Typical to use the default settings and installation location. Also compare the space that is required for installation with the actual space available in the installation directory. Note: You cannot customize the default settings, locations, or port numbers while upgrading from OpsCenter 7.0 (or 7.0.1) to OpsCenter 7.1. Click Next.

246

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

10 Specify a location for saving the old OpsCenter database. The default location
is C:\Program Files\Symantec\OpsCenter_SavedData. Click Browse to specify a different location. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist, you are prompted to create it. Click Yes to create the directory. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.

11 On the License Keys screen, enter the demo or permanent key that you have
received with the purchase of OpsCenter and click Add Key. Note: You can also add the license keys from the OpsCenter console. See About managing licenses on page 307. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. The license type information is also shown along with the key. More information about licenses is available. See About the OpsCenter licensing model on page 81.

12 Click Next. The Cluster Settings screen is displayed. 13 On the Cluster Settings screen, 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. This option is disabled. This option is disabled. This option is disabled. This option is disabled. Select LAN as a public network. You can select different public network for active and passive nodes.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

247

14 Click Next. The installer shows the summary of the settings that you have
selected for OpsCenter Server installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.

15 Click Install.
The installer starts installing the OpsCenter Server software. Note: In clustered mode, the default OpsCenter database location on Windows is the following location on the shared drive: OpsCenter\Server\db

16 After successful installation, you can view the OpsCenter console or view
installation logs.

17 Click Finish. Repeat this procedure for the passive nodes.

Uninstalling Symantec OpsCenter 7.1 from the Windows cluster

Use the Windows Add/Remove Programs utility to uninstall OpsCenter Server from a Windows cluster. Use the following procedure to uninstall OpsCenter from all the cluster nodes. 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. Log on to the cluster Web GUI. Right-click the selected cluster monitor panel and click Explorer View from the menu to access Cluster Explorer. Click the Service Groups tab in the Cluster Explorer configuration tree. Right-click the OpsCenter resource group and select Offline > All Systems. Click Yes to forcefully take the resource group offline. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter Server and click Remove. Click Next to continue and remove Symantec OpsCenter Server from your computer.

248

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

10 Uninstall OpsCenter software from all the nodes. Repeat steps 7 through 9
for all the passive nodes.

11 Delete the OpsCenter resource groups manually. Note that the installer does
not remove the OpsCenter resource groups. These must be removed manually. See Deleting OpsCenter resource group from the cluster on page 248.

Deleting OpsCenter resource group from the cluster

Use the following procedure to delete OpsCenter resource group from the cluster. To delete OpsCenter resource group from the cluster

1 2 3 4 5 6 7

Log on to the cluster Web GUI. Right-click the selected cluster monitor panel and click Explorer View from the menu to access Cluster Explorer. Click the Service Groups tab in the Cluster Explorer configuration tree. Right-click the OpsCenter resource group and select Offline > All Systems. Click Yes to forcefully take the resource group offline. Right-click the OpsCenter resource group and select Delete. Click Yes to delete the OpsCenter resource group.

Clustering Symantec OpsCenter Server on Solaris

This section provides information about installing OpsCenter Server in a clustered mode, on a Solaris host. Table 2-19 provides the Solaris clustering steps. 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. See Prerequisites for Symantec OpsCenter cluster on Solaris on page 249.

Make sure that you have met all prerequisites.

Make sure that your preinstallation See Preinstallation checklist for checklist is complete. a Symantec OpsCenter Server installation on page 251.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

249

Table 2-19 Step

4

OpsCenter Server clustering steps (continued) Description

Install OpsCenter 7.1.

Reference topic
See Installing Symantec OpsCenter Server in a clustered mode on Solaris on page 252.

Limitations of Symantec OpsCenter cluster on Solaris

An OpsCenter cluster has the following limitations:

Only the OpsCenter Server can be clustered.OpsCenter Agent and OpsCenter View Builder cannot be clustered. Upgrades from previous versions of NOM or VBR to clustered OpsCenter Server is not supported. You can upgrade from OpsCenter 7.0 (or 7.0.1) cluster to an OpsCenter 7.1 cluster. OpsCenter cluster cannot co-exist with any other Symantec product running in secure mode using the Symantec Product Authentication Service. OpsCenter does not support clustered AT.

Prerequisites for Symantec OpsCenter cluster on 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. For a list of supported storage devices, visit the following Web site: http://entsupport.symantec.com Verify that the supported version of VCS is correctly installed and configured on Solaris. Follow the steps in the Veritas Cluster Server Installation Guide. Verify that no VCS resource group and resource exist with the same name as that which you intend to use for OpsCenter. The SharedDisk must be configured and accessible to all cluster nodes where you want to install OpsCenter. Verify that you have an IP address and host name (virtual name) to be assigned to the OpsCenter resource in VCS. Only use these for the OpsCenter resource. Also, ping the IP address and verify that the IP address is not plumbed. Verify that you can mount the disk. Verify that you have the OpsCenter installation program and a valid license key.

250

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

Verify that OpsCenter Server installation is carried out with the domain admin account. Before installing OpsCenter Server, ensure that Symantec OpsCenter Agent 7.1 (PBX) and Symantec authentication service (AT) Server are installed separately on a remote host. PBX is installed when you install OpsCenter 7.1 Agent. Note the following points about installing OpsCenter Agent 7.1 (PBX) and AT on the remote host:

Symantec recommends that you first install OpsCenter Agent 7.1 (PBX) and then install AT from the OpsCenter 7.1 DVD. AT must be installed in a non-clustered mode. AT can be installed in Root + AB or AB mode on the remote host.

AT must be installed separately (and not along with OpsCenter) on the remote host. For more information about installing AT, see the Symanetc Infrastructure Core Services Installation Guide.

Verify that the authentication service and PBX components are connected. See Connecting Symantec Product Authentication Service and Symantec Private Branch Exchange on page 235.

Installing Symantec OpsCenter Agent 7.1 and AT on a remote host

OpsCenter Server requires that OpsCenter Agent 7.1 (PBX) and Symantec Product Authentication Service (AT) are installed on a standalone host, before OpsCenter can be clustered. Symantec recommends that you first install OpsCenter Agent 7.1 and then install AT from the OpsCenter 7.1 DVD. You must install the version of AT Service that is shipped with OpsCenter 7.1. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode. Symantec recommends that you configure AT in a 'Root+AB' mode. Clustered OpsCenter Server uses this authentication broker. To establish a connection between AT host and OpsCenter Server host, you need to create a principal user on the AT host. Use the credentials of this user when installing OpsCenter Server. Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server. You must upgrade to the version of authentication service that is shipped with OpsCenter.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

251

Note: OpsCenter does not support clustered AT. OpsCenter Agent 7.1 and AT can be installed on the remote host using the following procedure. To install AT

1 2

Log on to the remote host where you want to install OpsCenter Agent 7.1 and AT. Install OpsCenter Agent 7.1 on the remote host using the OpsCenter 7.1 DVD. See Installing Symantec OpsCenter Agent on UNIX on page 114.

To install AT, mount the OpsCenter 7.1 DVD. Navigate to the ICS directory:
cd ICS

Invoke the ./installics script from the ICS directory. The installics menu is displayed.

Select 1 to install AT. Note that you must enable PBX support for the authentication broker server. Answer y to enable Private Branch Exchange (PBX) support in authentication broker server. See Symantec Infrstructure Core Services Installation Guide for more details on using the installics script.

Preinstallation checklist for a Symantec OpsCenter Server installation

The OpsCenter Server requests certain cluster-related information during installation. Fill out the checklist before you begin installation. Note: The configuration utility unless specified, treats all attribute values globally. The following information is required for all VCS cluster configurations.
Virtual Name for NetBackup: IP address : Subnet mask Node Name IP address ---------------------------------------------------------------------------------------------------------------------Network device name (NIC)

252

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

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

About installation of Symantec OpsCenter with VCS

The following information is required if you use VCS. Review the scenario that is described. See Scenario 1 - with VxVM on page 252.

Scenario 1 - with VxVM

The following information is required if you use VCS with VxVM.
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, -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, you must install and configure OpsCenter in a clustered mode.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

253

Note: To install OpsCenter Server in clustered mode, first install the OpsCenter Server on the active node and then on the passive nodes. Also, you need to install OpsCenter Server manually on all the nodes. To install OpsCenter Server in clustered mode on Solaris

Fill out the checklist for all configurations and the checklist for your specific environment. See Preinstallation checklist for a Symantec OpsCenter Server installation on page 251.

2 3 4

Open a Solaris console and log on as root on the target host. Mount the OpsCenter product DVD for the appropriate platform on which you are installing OpsCenter Server. Make sure that the shared disk is not mounted on any node in the cluster. If applicable, unmount the OpsCenter shared mount point. Stop the volume the mount point is on and deport the disk group for that volume on all nodes of the cluster.

Type the following command:./install. Press Enter. Select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

6 7

The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter is already installed. The installer also examines the system for existing packages. The installer displays a list of components that are installed like PBX, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue. The installer prompts you with the following question:
Where do you want to install Symantec OpsCenter? </opt>

Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.

10 Type y to confirm the directory path and press Enter. 11 When OpsCenter Server is installed on the clustered setup, a confirmation
prompt is displayed.

254

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

When you install OpsCenter Server on the first node, you are prompted to confirm creation of an OpsCenter Server cluster. Type Yes to set up OpsCenter in HA mode. When you install OpsCenter Server on the subsequent nodes, information of already created NetBackup OpsCenter cluster group is displayed. You are prompted to join the group.

12 When you are prompted for cluster-specific configuration details, refer to

the checklist and provide details accordingly. Use the virtual name for the NetBackup server name. Caution: When you are prompted, you must provide the same virtual cluster name that you provided during the installation. This name is case-sensitive and must be in the same format (FQDN/short) on all the nodes.

13 Allow OpsCenter to be installed in a cluster. The following happens when

OpsCenter Server is installed:

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

Upgrading from OpsCenter 7.0 (or 7.0.1) cluster to OpsCenter 7.1 cluster
Use the following steps to upgrade from an OpsCenter 7.0 cluster to OpsCenter 7.1 cluster on Solaris. Note: To upgrade OpsCenter Server in a clustered mode, first install OpsCenter 7.1 Server on the active node and then on the passive nodes. Also, you need to install OpsCenter Server manually on all the nodes. To upgrade from OpsCenter 7.0 cluster to OpsCenter 7.1 cluster

Fill out the checklist for all configurations and the checklist for your specific environment. See Preinstallation checklist for a Symantec OpsCenter Server installation on page 251.

Log on to the OpsCenter 7.0 (or 7.0.1) cluster as root.

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

255

Make sure that the shared disk is not mounted on any node in the cluster. If applicable, unmount the OpsCenter shared mount point. Stop the volume the mount point is on and deport the disk group for that volume on all nodes of the cluster.

Offline OpsCenter server resource by using the following command:

hares -offline <opscenter server resource name> -sys <node>

Freeze OpsCenter group by using the following command:

hagrp freeze <OpsCenter group name> -persistent sys

Stop NetBackup OpsCenter cluster agent on all nodes of the OpsCenter group using the following command:
haagent -stop NetBackupOpsCenter -force -sys <node>

Log on to the active node and upgrade to OpsCenter Server 7.1 software. Mount the OpsCenter product DVD on the OpsCenter 7.0 (or 7.0.1) cluster that you want to upgrade.

Type the following command: ./install. Press Enter. Select Server from the displayed options (Server and Agent). Press Enter to install OpsCenter Server.

The Welcome message is displayed. Press Enter to continue. not. It prompts you in case OpsCenter Server is already installed. The installer also examines the system for existing packages.

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. (/var/symantec/)

Type the directory name in which the existing OpsCenter 7.0 database and configuration files can be saved and then press Enter. To accept the default directory path (/var/symantec), press Enter.

12 The installer displays a list of components that will be installed or upgraded

like PBX, AT, OpsCenter Server, OpsCenter GUI etc. Review this list and press Enter to continue.

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

Change to the following directory:

/opt/VRTS/install

Type the following command and press Enter:

./uninstallOpsCenterServer

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

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

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

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

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.

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

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.

Administering Symantec OpsCenter About OpsCenter database administration

271

To check the disk fragment count

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 . l o g /opt/SYMCOpsCenterServer/db/log/dbserver.log

Search for the word fragment in the file. For example, when you search for fragment in server.log or dbserver.log, you may find the following line:
Performance warning: Database file "G:\OpsCenter\db\vxpmdb.db" consists

Note: You may not find any results when you search for fragment. This result is completely fine. You may see such performance warnings when the disk fragment count is high.

Defragmenting the OpsCenter database

You can defragment the OpsCenter database using the dbdefrag command. Defragmentation helps to increase data access and retrieval speed. For optimum performance, defragment the OpsCenter databases once in a month and after a purge operation. Note: OpsCenter does not work during the time when the OpsCenter database is defragmented. To defragment the OpsCenter database on Windows and UNIX

Before you defragment the OpsCenter database, Symantec recommends that you back up the OpsCenter database. See Backing up the OpsCenter database on page 279.

To defragment the OpsCenter database on Windows, run the following command:

INSTALL_PATH\OpsCenter\server\bin\dbdefrag.bat

To defragment the OpsCenter database on UNIX, run the following command:

/opt/SYMCOpsCenterServer/bin/dbdefrag.sh

272

Administering Symantec OpsCenter About OpsCenter database administration

Configuring authentication server parameters

The authentication server parameters can be configured using the changeVxATProperties utility. Note: This procedure is applicable only for OpsCenter clusters where the authentication broker is remote. This procedure is not applicable when Symantec Product Authentication Service is installed on the local computer. To configure authentication server parameters

Enter the following command on Windows:

INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat

Enter the following command on UNIX:

/opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

The authentication server parameters appear one by one. The current values of the parameters are specified in brackets.

2 3

Enter the new values next to the respective parameter. If you do not enter a new value for a parameter, the value of the parameter does not change. You must restart the OpsCenter services for these changes to be effective. Answer y to restart the OpsCenter services.

Moving the OpsCenter database and database logs to a different hard disk
To improve OpsCenter performance, OpsCenter database files and the log files that are associated with the OpsCenter database should be stored on separate hard disks. You can store the OpsCenter database files on one hard disk and the log files on another hard disk. Symantec also recommends that you not store the database files on the hard disk that contains your operating system files. You can specify a custom location (non-default location) for the OpsCenter database during OpsCenter installation. The default location for the OpsCenter database can also be changed after OpsCenter has been installed. Use the following procedures to move the OpsCenter database and log files to a different hard disk. The first two procedures are for moving the OpsCenter database files on Windows or UNIX. The last two procedures are for moving the database log files.

Administering Symantec OpsCenter About OpsCenter database administration

273

To move the OpsCenter database to a different hard disk on Windows

Stop all OpsCenter services. Enter the following command:

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

Open the databases.conf file with a text editor like notepad from the following directory:
INSTALL_PATH\OpsCenter\server\db\conf

This file has the following contents:

"INSTALL_PATH\OpsCenter\server\db\data\vxpmdb.db"

This path specifies the default location of the OpsCenter database.

To move the database to a custom location like E:\Database, replace the contents of the file with the following:

"E:\Database\vxpmdb.db"

Make sure that you specify the path in double quotes. Also the directories in the specified path should not contain any special characters like %, ~, !, @, $, &, ^, # etc. For example, do not specify a path like E:\Database%. Save the databases.conf file.

Copy the database files to the new location. Copy vxpmdb.db and symcOpscache.db from INSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database. Restart all OpsCenter server services. To restart all OpsCenter services, enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete vxpmdb.db and symcOpscache.db from the default location (INSTALL_PATH\OpsCenter\server\db\data).

274

Administering Symantec OpsCenter About OpsCenter database administration

To move the OpsCenter database to a different hard disk on UNIX

Stop all OpsCenter server processes. Enter the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

The default location of the OpsCenter database is /opt/SYMCOpsCenterServer/db/data. Back up the OpsCenter database (/opt/SYMCOpsCenterServer/db/data) to some other location. Enter the following command:
cp R /opt/SYMCOpsCenterServer/db/data /backup/data

To move the database to a custom location like /usr/mydata, first create the new directory by entering the following command:
mkdir -p /usr/mydata

To move the database to a custom location like /usr/mydata, enter the following command:
mv /opt/SYMCOpsCenterServer/db/data/* /usr/mydata

Remove the symbolic link that exists for the OpsCenter database. Enter the following command:
unlink /opt/SYMCOpsCenterServer/db/data

Create a symbolic link to /usr/mydata in /opt/SYMCOpsCenterServer/db/data. To create a symbolic link, enter the following command:
ln -s /opt/SYMCOpsCenterServer/db/data /usr/mydata

Restart all OpsCenter server processes by entering the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete vxpmdb.db and symcOpscache.db from /backup/data.

Administering Symantec OpsCenter About OpsCenter database administration

275

To move the database log files to a different hard disk on Windows

Stop all OpsCenter server services. Enter the following command:

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

Navigate to the following location for 32-bit and 64-bit systems respectively:
INSTALL_PATH\OpsCenter\server\db\WIN32 INSTALL_PATH\OpsCenter\server\db\WIN64

Enter the following commands:

dblog -t directory_path\vxpmdb.log database_path\vxpmdb.db

where directory_path is the path where you want to store the database logs and database_path is the path where your database is located. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). It is recommended to use vxpmdb.log as the name of the log file.

Restart all OpsCenter server services. To restart all OpsCenter services, enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

To move the database log files to a different hard disk on UNIX

Stop all OpsCenter server processes. Enter the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

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

276

Administering Symantec OpsCenter Configuring remote authentication service in OpsCenter

Navigate to the following location:

/opt/SYMCOpsCenterServer/db/bin

Enter the following commands:

./dblog -t directory_path/vxpmdb.log database_path/vxpmdb.db

where directory_path is the path where you want to store your database log file and database_path is the path where the OpsCenter database is located. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). It is recommended to use vxpmdb.log as the name of the log file.

Restart all OpsCenter server processes by entering the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

About database troubleshooting

Security information about the OpsCenter database is available. 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. See About OpsCenter log files on Windows servers on page 296. See About OpsCenter log files on UNIX servers on page 298.

Configuring remote authentication service in OpsCenter

OpsCenter supports using Symantec Product Authentication Service (AT) remotely. When you are using the Symantec Product Authentication Service remotely, you install the authentication server component on a remote computer in the network. If you were using a remote AT configuration in NOM and upgrade to OpsCenter, you can configure the remote AT after upgrading to OpsCenter. Use the following procedure to configure remote AT with OpsCenter.

Administering Symantec OpsCenter Configuring remote authentication service in OpsCenter

277

To configure remote authentication service in OpsCenter

Enter the following command for Windows and UNIX platforms respectively:
Windows UNIX INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat /opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

The authentication server parameters appear one by one. The current values of the parameters are specified in brackets. 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. Authentication Service Port Number The port number of the server on which the authentication service server component is running. The default value is 2821. Authentication Service Domain Name The domain name of the broker. The default value is broker. Authentication Service User Name The name of the broker that the user used for initial authentication. The default value is admin. Authentication Service Password The password of the broker that the user used for initial authentication. The default value is Vxadmin.

278

Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics

To use a remote AT configuration, enter the new values next to the respective parameter. If you do not enter a new value for a parameter, the value of the parameter does not change.
Authentication Service Host Name Enter the FQHN of the remote server on which the authentication service server component is running. Enter the port number of the remote server on which the authentication service server component is running. Enter the domain name of the broker. Enter the name of the broker that the user used for initial authentication. Enter the password of the broker that the user used for initial authentication.

Authentication Service Port Number

Authentication Service Domain Name Authentication Service User Name

Authentication Service Password

You must restart the OpsCenter services for these changes to be effective. Answer y to restart the OpsCenter services.

About backup and restore of OpsCenter 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 Backing up OpsCenter in case of a disaster on page 278. See Restoring OpsCenter on page 281.

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.

Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics

279

To back up OpsCenter in case of a disaster

Take a hot backup of the OpsCenter database (vxpmdb.db and symcOpscache.db) using the dbbackup script. This script can be run whenever you need to back up your OpsCenter database. See Backing up the OpsCenter database on page 279.

Along with the OpsCenter database, the user information that Symantec Product Authentication Service manages must be saved in a directory or by using a NetBackup backup policy. See Saving the OpsCenter user profiles managed by Symantec Product Authentication Service on page 280. Note: You can also create schedules for taking regular database and authentication profile backups. In this case, NetBackup policies can be created to back up the specified directories that contain OpsCenter database snapshots and the authentication service user configuration files. See the NetBackup Administrators Guide, Volume I for more information on how to configure a policy and schedule.

If you want to change the OpsCenter database password, you also need to back up the database password file.

Backing up the OpsCenter database

OpsCenter is shipped with a database backup script that performs backup of the database without interrupting its operations, which is referred to as hot backup. On UNIX as well as Windows platforms, the script overwrites existing database (db) files before backing up or restoring the database. The database files are as follows: vxpmdb.db, symcOpscache.db, and vxpmdb.log. The script backs up or restores the vxpmdb.db, symcOpscache.db, and vxpmdb.log file (if it exists). Note: Regular file system backups are not sufficient for backing up the OpsCenter database. You must schedule periodic hot backups for the OpsCenter database to avoid losing any important data.

280

Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics

To back up the OpsCenter database

Log on to the OpsCenter database server host in one of the following ways:
Windows UNIX As an administrator or user in the Administrator group root

2 3

Open the Windows command prompt or the UNIX console. Run the backup script that is appropriate for your platform. Specify one of the following backup directories depending on your platform:
Windows INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat C:\MyDbBackupFolder /opt/SYMCOpsCenterServer/bin/dbbackup.sh /my_db_backup_dir

UNIX

The backup script creates vxpmdb.db, symcOpscache.db, and vxpmdb.log (if it exists) in the backup directory that you specified.

Saving the OpsCenter user profiles managed by Symantec Product Authentication Service
Use the following procedures to save the authentication service profiles on Windows and UNIX servers. To save authentication service profiles on Windows servers

Do one of the following to save the user profiles:

Copy the folder

INSTALL_PATH\VERITAS\Security\Authentication\systemprofile to

another folder.

Create a NetBackup job policy to back up the authentication service systemprofile folder.

To save authentication service profiles on UNIX servers

Do one of the following to save the user profiles:

Copy the folder /var/VRTSat to another folder. Create a NetBackup job policy to back up the authentication service profile folder.

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, you need to back up the following password file (along with the backup of the OpsCenter database files and authentication service profile folders). To back up the OpsCenter database password file on Windows

Back up the db.conf file that is located in

INSTALL_PATH/OpsCenter/server/config directory.

To back up the OpsCenter database password file on UNIX

Back up the db.conf file that is located in /opt/SYMCOpsCenterServer/config directory.

Restoring OpsCenter
A restore of OpsCenter requires that the new OpsCenter server has the same host name and IP address of the old server that crashed. This limitation is due to a couple of reasons. Some of the reasons are the following:

The authentication service credentials (host name and IP address) are stored on the old OpsCenter server. To enable data collection, you must configure the master servers for data collection. This involves adding the OpsCenter hostname to the Server List of the NetBackup master servers. Atter this, you must add the master servers to the OpsCenter console. See Adding a master server in OpsCenter on page 377.

Note: The following procedures assume that you have OpsCenter database snapshots and the authentication service user profiles saved in folders. The sequence of steps gives an overview about the steps that need to be followed to restore OpsCenter. To restore OpsCenter in case of a disaster

1 2

Install OpsCenter on a server with the same name as the server where problems happened. Stop all OpsCenter server services.

282

Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics

Restore the OpsCenter database snapshot files and authentication service user profiles from the backup image. See Restoring the OpsCenter database on page 282. See Restoring the OpsCenter user profiles managed by Symantec Product Authentication Service on page 284.

If you saved a copy of the OpsCenter database password file, copy the file to the corresponding location on the newly installed OpsCenter server. Copy the db.conf file to INSTALL_PATH/OpsCenter/server/config directory on Windows or /opt/SYMCOpsCenterServer/config directory on UNIX. Restart all OpsCenter server services.

Restoring the OpsCenter database

After you back up the database, you can restore it. On Windows and UNIX hosts, the restore operation automatically stops the database, restores the backup database files, and restarts the database. The dbbackup script overwrites existing database (db) files before backing up or restoring the database. The database files are as follows: vxpmdb.db, symcOpscache.db, and vxpmdb.log. The script backs up or restores the vxpmdb.db, symcOpscache.db, and vxpmdb.log file (if it exists).

Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics

283

To restore a backed up OpsCenter database

On the OpsCenter server with backup data you want to restore, open a UNIX console or a Windows command prompt and log on as root (on UNIX) or as an administrator or user in the Administrators group (on Windows).
Windows Open a Windows command prompt and log on as an administrator or user in the Administrators group. Open a UNIX console and then log on as root.

UNIX

All the paths that are shown in the steps that follow are the default database install paths. These paths may different for your site if the database was installed anywhere other than the default location.

To restore the backed up database, do one of the following:

Windows Type the following command and press Enter. INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat <backupDir> -restore <restoreDir> UNIX Type the following command and press Enter. /opt/SYMCOpsCenterServer/bin/dbbackup.sh <backupDir> -restore <restoreDir>

where backupDir is the directory where the backed up database resides, and <restoreDir> is the location of the current OpsCenter database. restoreDir is optional. If not used, the dbbackup script restores to the default database directory:
Windows UNIX INSTALL_PATH\OpsCenter\server\db\data /opt/SYMCOpsCenterServer/db/data

If you specified a non-default directory location, you must specify the restoreDir option. The script prompts you with a message similar to the following:
WARNING: this operation will overwrite the active OpsCenter data on this host. Do you wish to continue ? [y/n] (n)

284

Administering Symantec OpsCenter About communication and firewall considerations

To continue with the restore, press Enter on Windows hosts. To continue with the restore, type y on UNIX hosts. The dbbackup script automatically stops and restarts the database.

Restoring the OpsCenter user profiles managed by Symantec Product Authentication Service
Use the following procedures to save the authentication service profiles on Windows and UNIX servers. To restore the authentication user profiles on Windows

Stop all OpsCenter server services. Enter the following command:

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

2 3

Copy or overwrite the folder containing the authentication service user profiles to INSTALL_PATH\VERITAS\Security\Authentication\systemprofile. Start all OpsCenter server services. Enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

To restore the authentication user profiles on UNIX

Stop all OpsCenter server processes. Enter the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

2 3

Copy or overwrite the folder containing the authentication service user profiles to /var/VRTSat Start all OpsCenter server processes. Enter the following command:
/opt/SYMCOpsCenterServer/bin/opsadmin.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 - Port 80 and Port 443, Port 8181 and Port 8443, and, Port 8282 and Port 8553. 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, PureDisk etc. 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.

Communication ports used by key OpsCenter components

The following table shows the default port settings for OpsCenter.

286

Administering Symantec OpsCenter About communication and firewall considerations

SMTP recipient ports can be configured from the OpsCenter console (using Settings > Configuration > SMTP Server). The SNMP trap recipient ports can also be configured from the OpsCenter console (using Settings > Recipients > SNMP). If these ports are changed then the appropriate hardware ports have to be opened. Table 3-8 lists the communication ports that are used by key OpsCenter components. 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.

Destination Port Number Host

Mail server 25

SNMP Server 162

SNMP trap recipient PBX (pbx_exchange)

Allow from source to destination.

NetBackup Master Server(s)

1556

Allow between source and destination (bi-directional). PBX port number configuration is supported. See About OpsCenter Web GUI to OpsCenter server software communication on page 289.

OpsCenter Client

OpsCenter Server

1556

PBX (pbx_exchange)

Allow between source and destination. Some hardened servers and firewall configurations may block this port. PBX port number configuration is not supported. See About OpsCenter Web GUI to OpsCenter server software communication on page 289.

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.

Source Host

Destination Port Number Host

Web browser OpsCenter Server

The following HTTP and HTTP and HTTPS HTTPS ports are checked for availability in the specified sequence and the first available port combination is used by default:

80 (HTTP) and 443 (HTTPS) 8181 (HTTP) and 8443 (HTTPS) 8282 (HTTP) and 8553 (HTTPS) Sybase database Allow between source and destination. (dbsrv11) Some hardened servers and firewall configurations may block this port. Symantec Allow between source and destination in case Product NBAC is enabled on NetBackup master server. Authentication Service (vxatd)

OpsCenter Server

OpsCenter Server

13786

OpsCenter Server

Host where 2821 Symantec Product Authentication Service (AT) Server is installed

Ports required to communicate with backup products

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

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. 13782 port should be used to connect to the NetBackup master server and 13724 port should be used to respond to the Agent host. The response is sent on a port in the reserved port range 512-1023 if not configured to use vnetd The following processes are used for NetBackup data collection:

Port number
13782 & 13724

bperror.exe bpretlevel.exe bpimagelist.exe 6106

Backup Exec

OpsCenter (Backup Exec data collector) communicates with Backup Exec Server using Backup Exec API

PureDisk

OpsCenter (PureDisk data collector) 443 (HTTPS) communicates with PureDisk SPA 2821 (AT) using atssl OpsCenter (TSM data collector) communicates with TSM Server using TSM CLI dsmadmc 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. These protocols use TCP/IP. For HTTP, specific ports are checked for availability in a particular sequence and the first available port is used by default.

Administering Symantec OpsCenter About communication and firewall considerations

289

Table 3-10 lists how the default HTTP and HTTPS ports are selected. Table 3-10 Sr. No.
1.

Default HTTP and HTTPS ports HTTPS port number

443

HTTP port number

80

Description
Port 80 and Port 443 are checked for availability. If port 80 and port 443 are available, port 80 is used as the default HTTP port and port 443 is used as the default HTTPS port. In case, some other application like a Web server uses one or both ports, then the next port combination is checked for availability.

2.

8181

8443

Port 8181 and Port 8443 are checked for availability. If port 8181and port 8443 are available, port 8181 is used as the default HTTP port and port 8443 is used as the default HTTPS port. In case another application like VRTSWeb installed with VCS or any other product uses one or both ports, then the next port combination is checked for availability.

3.

8282

8553

Port 8282 and Port 8553 are checked for availability.

These HTTP and HTTPS ports are opened only for input and are configurable using the command lines. See configurePorts on page 745.

About OpsCenter Web GUI to OpsCenter server software communication

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

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. The OpsCenter server software collects data from NBSL in the following ways:

Initial data load Listening for change notifications or events

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

About SNMP traps

SNMP trap protocol is used for outbound UDP traffic and requires a port that opens for output. The port number is 162.

About OpsCenter Web GUI/OpsCenter server to Sybase database communication

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

About OpsCenter Web GUI to OpsCenter server email communication

SMTP email server protocol is used for outgoing mail. The port number is defined when the user specifies the SMTP server port (see Settings > Configuration >

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.

Gathering troubleshooting data with the support script

If you are running OpsCenter on UNIX or Windows, you can use the support script to gather troubleshooting information for OpsCenter Server and OpsCenter Agent. The script collects Server and Agent logs, collects information about any data collection problems, captures the current Agent configuration, and compresses the results into a zip file. This file can serve as a first-level information for the Support team in case of an issue with OpsCenter. To gather troubleshooting data for OpsCenter Server on Windows

Run the following command to execute the support script for OpsCenter Server:
INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport.bat

Note: The following is the default directory location on Windows computers.

The script then prompts the following questions:

Do you want to collect configuration files? [y/n] y Do you want to collect application log files? [y/n] y Do you want to collect OpsCenter GUI <147> log files? [y/n] y Do you want to collect OpsCenter Server <148> log files? [y/n] y Do you want to collect db log files? [y/n] y Do you want to collect WebServer log files? [y/n] y Do you want to collect setEnv file? [y/n] y Do you want to collect database files? [y/n] y If this is an upgrade scenario, do you want to collect old database and

If this is an install scenario, do you want to collect installation logs

Answer y or n based on your preferences.

292

Administering Symantec OpsCenter Gathering troubleshooting data with the support script

This script collects system information and OpsCenter configuration information based on your preferences. It then compresses all this information in a file that is called Support.zip. You can use OpsCenter and run the support script in the background. Note: Adding log files and OpsCenter database files can increase the file size of the resulting Support.zip file.

The Support.zip file is stored in the following directory:

INSTALL_PATH\OpsCenter\server\temp\support

To gather troubleshooting data for OpsCenter Agent on Windows

Run the following command to execute the support script for OpsCenter Agent:
INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport.bat

Note: The following is the default directory location on Windows computers.

2 3

The script stops the OpsCenter Agent service and then collects the OpsCenter Agent logs. It then collates this information in a Support.zip file. This zip file is stored in the following directory:
INSTALL_PATH\OpsCenter\Agent\temp\support

After the Support.zip file is created, the script starts the OpsCenter Agent service.

Administering Symantec OpsCenter Gathering troubleshooting data with the support script

293

To gather troubleshooting data for the OpsCenter Server on UNIX

Run the following commands to execute the support scripts for OpsCenter Server:
/opt/SYMCOpsCenterServer/bin/opsCenterSupport.sh

The script then prompts the following questions:

Do you want to collect configuration files? [y/n] y Do you want to collect application log files? [y/n] y Do you want to collect OpsCenter GUI <147> log files? [y/n] y Do you want to collect OpsCenter Server <148> log files? [y/n] y Do you want to collect db log files? [y/n] y Do you want to collect WebServer log files? [y/n] y Do you want to collect setEnv file? [y/n] y Do you want to collect database files? [y/n] y If this is an upgrade scenario, do you want to collect old database and

If this is an install scenario, do you want to collect installation logs

Answer y or n based on your preferences.

This script collects system information and OpsCenter configuration information based on your preferences. It then collates all this information in a support.zip file. You can use OpsCenter and run the support script in the background. Note: Adding log files and OpsCenter database files can increase the file size of the resulting support.zip.

The support.zip file is stored in the following directory:

/opt/SYMCOpsCenterServer/temp/support

294

Administering Symantec OpsCenter About OpsCenter log files

To gather troubleshooting data for the OpsCenter Agent on UNIX

Run the following command to execute the support script for OpsCenter Agent:
/opt/SYMCOpsCenterAgent/bin/opsCenterAgentSupport.sh

Note: The following are the default directory locations on UNIX machines.

2 3

The script stops the OpsCenter Agent process and then collects the OpsCenter Agent logs. It then collates this information in a support.zip file. The support.zip file is stored in the following directory:
/opt/SYMCOpsCenterAgent/temp/support

After the zip file is created, the script automatically starts the OpsCenter Agent process.

About OpsCenter log files

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

About VxUL log files

The VxUL log file creates log file names and messages in a format that is standardized across all Symantec components. These messages use VxUL IDs (a product ID and an originator ID) that identify the component that wrote the log message. OpsCenter components create most log messages in VxUL format. Table 3-11 shows the originator IDs used by OpsCenter and key shared components. 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

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, OpsCenter writes VxUL logs to the following directory:

INSTALL_PATH\OpsCenter\server\logs

In UNIX, OpsCenter writes VxUL logs to the following directory:

/opt/SYMCOpsCenterServer/logs

You can control how OpsCenter writes log files for OpsCenter Server, OpsCenter Agent, and the OpsCenter Web GUI. The following OID values must be used for OpsCenter Server, OpsCenter Agent, and OpsCenter Web GUI.
OpsCenter Server OpsCenter Agent OpsCenter Web GUI 148 146 147

Table 3-12 lists the commands by which you can control logging on Windows. Table 3-12 Control Logging Control logging on Windows Command

To change the log directory destination INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.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\server\logs) To configure the verbosity level (default INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.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.exe -a -p 58330 -o <OID> -s DiagnosticLevel=1 INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s NumberOfLogFiles=100

296

Administering Symantec OpsCenter About OpsCenter log files

Table 3-13 lists the commands by which you can control logging on UNIX. 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.

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.

About OpsCenter 7.1 installation log files

Table 3-14 shows details about the installation log files for OpsCenter components. These log files can be used to troubleshoot installation issues of the respective OpsCenter component. Table 3-14 OpsCenter 7.1 installation log files

OpsCenter Log file component

OpsCenter Server OpsCenter Agent OpsCenter View Builder %ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS \OpsCenterServerInstallLog.html %ALLUSERSPROFILE%\\Symantec\OpsCenter\INSTALLLOGS \OpsCenterAgentInstallLog.html %ALLUSERSPROFILE%\\Symantec\OpsCenter\INSTALLLOGS \OpsCenterViewBuilderInstallLog.html

Administering Symantec OpsCenter About OpsCenter log files

297

About OpsCenter log files

Table 3-15 shows details about the OpsCenter log files. Table 3-15 Log file directory
INSTALL_PATH\ OpsCenter\server\ logs\

OpsCenter log files Log file Troubleshooting purpose

ServerService_timestamp.log These log files for system.err and system.out of OpsCenter server service.

About log files associated with Symantec Product Authentication Service

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

On 32-bit Windows vxatd.log platforms: %ProgramFiles% vssconfig.log \Veritas\Security \Authentication\bin On 64-bit Windows platforms: %ProgramFiles(x86)% \Veritas\Security \Authentication\bin

About OpsCenter database log files

Table 3-17 lists the log files that are associated with the OpsCenter database. 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

Troubleshooting purpose
OpsCenter Sybase database activity. OpsCenter Sybase database transaction files.

vxpmdb.log

Note: Do not change this log file.

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.

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. Table 3-18 Log file directory Log files associated with VxUL and other components Log file Troubleshooting purpose
PBX activity. NBSL activity.

INSTALL_PATH\VERITAS\VxPBX\bin\ 50936-103-*.log INSTALL_PATH\VERITAS\NetBackup\ 51216-132-*.log logs\ INSTALL_PATH\OpsCenter\Agent\logs 51216-146-*.log INSTALL_PATH\OpsCenter\gui\logs\ 51216-147-*.log

Agent activity. OpsCenter Web GUI activity. OpsCenter server activity.

INSTALL_PATH\OpsCenter\server\logs 58330-148*.log

About OpsCenter log files on UNIX servers

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

About log files associated with OpsCenter

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

OpsCenter log file

/opt/SYMCOpsCenterServer/logs/ OpsCenterServer_out.log /opt/SYMCOpsCenterServer/logs/ purge-status.log /var/VRTS/install/logs/ (directory)

Provides a trace for any installation issues.

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. Table 3-20 Log file
/var/VRTSat/vxatd.log

Log files for Symantec Product Authentication Service Troubleshooting purpose

Authentication activity.

About log files associated with OpsCenter database

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

OpsCenter log file

/opt/SYMCOpsCenterServer/db/log/ dbserver.log

/opt/SYMCOpsCenterServer/db/data/ OpsCenter Sybase database transaction files. vxpmdb.log Note: Do not change this log file.

About log files associated with OpsCenter Web server

Table 3-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).

About log files associated with VxUL and other components

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

OpsCenter log file

/opt/VRTSpbx/log/50936-103-*.log /opt/openv/logs/51216-132-*.log

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 /opt/SYMCOpsCenterGUI/logs/ 51216-147-*.log /opt/SYMCOpsCenterServer/logs/ 558330-148*.log

OpsCenter Web GUI activity.

OpsCenter server activity.

Chapter

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

302

Understanding OpsCenter settings OpsCenter settings

OpsCenter settings
This topic describes the various OpsCenter settings. An OpsCenter Admin can configure these settings using the OpsCenter console. The normal users can view or access the information that is relevant only to their profiles, which the OpsCenter Administrator has set. You can configure the following settings in OpsCenter. Table 4-1 Setting Settings in OpsCenter Lets you... Reference topic

User Preferences Add user-specific details and create user See Setting user profiles. preferences on page 304. NetBackup Add NetBackup master servers and their See About configuring data properties to collect data from it. collection for NetBackup on page 361. Create Agent and Data Collectors to collect data from non-NetBackup products. See About managing OpsCenter Agents on page 353.

Agent

License

Manage permanent or demo license keys. See Adding OpsCenter license keys on page 308. Specify when you want to purge the data See Configuring the data that is collected from various products. 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. Configure Symantec ThreatCon feature in OpsCenter. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is. See Configuring Symantec ThreatCon feature in OpsCenter on page 312.

Data Purge

SMTP Sever

ThreatCon

Host Alias

Add aliases for hosts.

See Adding host aliases in OpsCenter on page 313.

Object Merger

Configure OpsCenter to merge the objects See Merging objects (hosts) that represent the same backup client, in OpsCenter on page 315. but registered as separate objects

Understanding OpsCenter settings OpsCenter settings

303

Table 4-1 Setting

Tape Library

Settings in OpsCenter (continued) Lets you...

Modify tape library information

Reference topic
See Merging objects (hosts) in OpsCenter on page 315. See Copying a user profile in OpsCenter on page 317.

Copy User Profile Configure OpsCenter to copy a user's profile to another user. Report Export Location

Specify the location where the exported See Setting report export reports are stored. location in OpsCenter on page 318. Add new object types and attributes. See About managing Object Types in OpsCenter on page 319. See About managing OpsCenter views on page 414. See About managing Symantec OpsCenter users on page 321. See About managing recipients in OpsCenter on page 330.

Object Type

Views

Create and manage OpsCenter views.

Users

Manage users and user groups.

Recipients

Manage Email and SNMP recipients.

Currency Settings

Manage the currency settings that appear See Setting the default in cost reports. You can select a currency currency for OpsCenter cost from the global currency list and set it as reports on page 337. default. Create cost variables. See Settings > Chargeback > Cost Variable options on page 339. See Settings > Chargeback > Cost Formulae options on page 343. See Estimating chargeback costs using the OpsCenter Formula Modeling Tool on page 344.

Cost Variables

Cost Formulae

Create cost formulae.

Cost Estimation

Manage cost estimation.

304

Understanding OpsCenter settings Setting user preferences

Setting user preferences

In OpsCenter, you can set your preferences, such as default locale or time zone and personal details, such as email ID or name. You can also change your password using the User Preferences tab, if your user account belongs to the OpsCenterUsers domain. To set user preferences

1 2

In the OpsCenter console, click Settings > User Preferences. The user preferences options are organized in the General and My Profile tabs. Click the General tab to set Default Locale, Data Display Time Zone, Start 24 Hour Day at, Disable Auto Refresh, Auto Refresh Interval (Minutes), and Allow Multiple Selection in View Pane. Click Save. Click the My Profile tab to see or modify User Name, Password, User Role, Domain Name, and Email Address. In General details, you can type in name and contact information for this user.

3 4

Click Save.

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. For example, if you select English as a default locale, all OpsCenter GUI screens use English as a default language. Select a preferred time zone - either OpsCenter Server time zone or any other time zone from the Other drop-down list. OpsCenter displays time on the GUI screens according to the selected time zone. Enter the time that is used as the start time of a day in reports. Report data is grouped depending on this start time. Select this check box if you do not want to automatically refresh the OpsCenter GUI. By default, the auto-refresh option is enabled.

Data Display Time Zone

Start 24 Hour Day at

Disable Auto Refresh

Understanding OpsCenter settings Setting user preferences

305

Table 4-2 Option

General options (continued) Description

Enter auto-refresh interval in minutes. For example, if you want to refresh the OpsCenter GUI to show updated data after every 5 minutes, enter five in the Auto Refresh Interval text box.

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. When you check this option, you can see a check box next to each master server or node in the View Pane. To view data for multiple master servers and nodes, you check the corresponding check boxes and then click Apply Selection. By default, the multiple-selection option is enabled. When you uncheck the multiple-selection option, you can only select a single node or view object from the View Pane at a given time. You can make selections in the View pane in a similar manner as NetBackup Operations Manager (NOM). Each node or a view object is a link. You can click a node or a view object to view data for the respective node or view object. For example, you can click a master server in the View Pane to view data for the specific master server. See About making multiple or single-click selections in the View pane on page 63. When you uncheck the multiple-selection option, a Group Component Summary table is displayed when you click Monitor > Jobs and select Summary View from the drop-down list. The Group Component Summary table was also displayed in NOM earlier. The Group Component Summary table at the bottom of the view displays job summary information. It shows the immediate NetBackup constituents of the selected view or node (group) in the View pane. For example if you select the ALL MASTER SERVERS view, the Group Component Summary table displays job summary for each master server. More details about the Group Component Summary table are available. See About the Group Component Summary table on page 445.

306

Understanding OpsCenter settings Setting user preferences

Table 4-2 Option

General options (continued) Description

With OpsCenter 7.1, you can export a tabular report in various PDF formats. 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. Landscape Displays a maximum of ten columns of data per page. 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. Expand to fit Displays the entire data across a single page.

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. The OpsCenter security admin sets a default password for each user when it creates the profiles. The users that belong to the OpsCenterUsers domain can change their passwords after logging on . To change password, click the Change Password link. See Changing your OpsCenter password on page 307. The users from other domains cannot change their passwords using this option.

User Role Domain Name Email Address General Details

The role of this user. The name of the domain to which this user belongs. The email address of this user. Fill in the First Name, Last Name, Cost Center, Department, Work Number, Mobile Number, and Pager Number.

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. Change the password at regular intervals thereafter. To change your OpsCenter password

1 2 3

In the OpsCenter console, click Settings > My Profile. In the My Profile dialog box, click Change Password. In the Change Password dialog box, do the following:

Type the existing password in the Old Password field. Type the new password in the New Password field. Passwords are case-sensitive and must contain at least five characters.

Type your new password again in the Confirm New Password text box.

Click Save.

About managing licenses

To use the advanced features that are not available in Symantec OpsCenter, you need to use a license key and enable Symantec OpsCenter Analytics. See About Symantec OpsCenter on page 23. See Adding OpsCenter license keys on page 308. See Viewing OpsCenter license keys on page 308. See Deleting OpsCenter license keys on page 308.

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, EVALUATION etc. Expiry date that is associated with the license key. Licensed features that are associated with the key.

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. Actual current usage of the licensed feature. Total licensed value that is associated for the specific licensed feature.

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. You can add one or more OpsCenter license keys. To add OpsCenter license keys

1 2 3 4 5

Log on to the OpsCenter console as admin. In the OpsCenter console, click Settings > Configuration. Click the License tab. Click Add. On the Add License Key pop-up screen, enter a license key and click OK.

Viewing OpsCenter license keys

You can view the license keys that are installed on the OpsCenterserver host. To view OpsCenter license keys

1 2 3

Log on to the OpsCenter console as admin. In the OpsCenter console, click Settings > Configuration. Click the License tab.

Deleting OpsCenter license keys

You can remove one or more Symantec OpsCenter Analytics license keys from the OpsCenter Server, on which you are connected as an administrator. To delete Symantec OpsCenter Analytics license keys

1 2

Log on to the OpsCenter console as admin. In the OpsCenter console, click Settings > Configuration.

Understanding OpsCenter settings Configuring the data purge period on the OpsCenter Server

309

3 4 5

Click the License tab. Select the check box in front of the license key that you want to delete. Click Delete.

Configuring the data purge period on the OpsCenter Server

You can configure the OpsCenter Server retention periods for the data types that are logged, such as Job, Policy, and Skipped Files. Note: The details of the purged data are stored in the purge-status.log file, which is located in the OpsCenter server logs directory. To configure the data purge period on the OpsCenter Server

1 2 3

Log on to the OpsCenter console as admin. In the OpsCenter click Settings > Configuration. Click the Data Purge tab. By default, data purge is enabled.

Edit the default data purge settings as necessary. See Settings > Configuration > Data Purge options on page 309.

5 6

In the Time of Purge text box, enter the time of day (in 24-hour clock format) when you want to purge the data. Click Save.

Settings > Configuration > Data Purge options

By default, data purge is enabled. Edit the default data purge options as follows:

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. The number of days set for backup logs should be less than or equal to the number of days set for backup jobs. In other words, logs can be purged earlier than their respective jobs, or they can be purged at the same time.

Note: If logs are purged but the respective jobs are not
purged, the corresponding logs are collected again. For example: The data purge setting for backup jobs is set to 10 days and for Backup Logs are five days. The backup logs are purged after five days but the related jobs are still present. Because, the backup jobs are set to be purged after 10 days. Thus, the logs of such jobs are collected again by the OpsCenter Agent. Backup Log Set the number of days after which you want to purge the Backup logs. Set the number of days to retain Tape Drive History logs. Set the number of days to retain Media History logs. Enter the number of days for which you want to retain the alert data. Alert data older than this number is purged from the OpsCenter database. Number of days for which the SLP data should be retained. Number of days for which you want to retain the audit trail records.

Tape Drive History Media History Alert

SLP Images Audit Trail

Note: By default, data purge is set to 420 days.

Time of Purge Enter the time of day (in 24-hour clock format) when you want to purge the data.

Restarting the OpsCenter service after upgrading to Server 7.1

While upgrading from NOM or VBR to OpsCenter Server 7.1, the OpsCenter Server service and the data migration process start simultaneously. Since the data migration from NOM or VBR to the OpsCenter database has just started and is

Understanding OpsCenter settings Configuring SMTP server settings for OpsCenter

311

not complete, the purge settings in OpsCenter take default values and not the values that you configured in NOM or VBR. To use the purge settings that you configured for NOM or VBR in OpsCenter 7.1, you must restart the OpsCenter Server service after the data migration is complete. Use the following procedure to restart OpsCenter Server service after the data migration is complete on Windows and UNIX platforms. To restart the OpsCenter Server service on Windows

1 2

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

To restart the OpsCenter Server process on UNIX

Enter the following command to stop the OpsCenter Server process:

/opt/SYMCOpsCenterServer/bin/stopserver

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. To configure SMTP server settings for OpsCenter

1 2 3

Log on to the OpsCenter console as admin. In the OpsCenter console, click Settings > Configuration. Click SMTP Server. OpsCenter uses these global server settings to send email notifications using the SMTP server that you specify.

Enter the required information. See Settings > Configuration > SMTP Server options on page 311.

Click Save.

Settings > Configuration > SMTP Server options

A description of the Settings > Configuration > SMTP Server options follows in the table.

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. Notifications of the alerts that are generated in OpsCenter are sent using this SMTP server.

SMTP Server Name

SMTP Server port

Enter the SMTP (Simple Mail Transfer Protocol) Server port number. Enter the name that is associated with the email ID. For example, Backup Reporting Department. Specify the email ID to receive any replies to the alerts or the reports that were sent by OpsCenter. Some SMTP servers may require user name and password credentials to send email. Enter the user name.

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. Enter the password for this user account.

Configuring Symantec ThreatCon feature in OpsCenter

This section provides information on how to configure the Symantec ThreatCon feature in OpsCenter. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is. See About the Symantec ThreatCon pane on page 65. Use the following procedure to enable or disable the Symantec ThreatCon feature. The ThreatCon feature is enabled by default. To disable ThreatCon, uncheck the box next to Enable ThreatCon Collection. To configure Symantec ThreatCon feature in Windows for OpsCenter

1 2 3

Log on to the OpsCenter console with administrator privileges. In the OpsCenter, click Settings > Configuration. Click ThreatCon.

Understanding OpsCenter settings Adding host aliases in OpsCenter

313

Edit the default information. See Settings > Configuration > ThreatCon options on page 313.

Click Save.

Settings > Configuration > ThreatCon options

A description of the Settings > Configuration > ThreatCon options follows in the table. Table 4-7 Option ThreatCon options Description

EnableThreatConCollection Disable or enable the ThreatCon data collection using this check box. Polling Interval Server Name Set the minutes for Polling Interval.

Note: The proxy server configuration is not mandatory.

Enter the following proxy server details if you want to use it for accessing the latest ThreatCon ratings, if the default network is down. Enter the proxy server name.

Port User Name Password

Enter the port number to connect to the proxy server. Enter the user name of the proxy server. Set the password for the user account that you use to connect to the proxy server.

See Configuring Symantec ThreatCon feature in OpsCenter on page 312.

Adding host aliases in OpsCenter

This section provides the procedures to add aliases for hosts. The hosts primary alias is displayed in all console functions and reports. Other host aliases are used when you are search in OpsCenter or gather and collate data.

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. For example, if you use an alias that is unknown to OpsCenter, the explorer stops collecting information from the OpsCenter host. Instead the explorer attempts to collect data from a host with the alias name. To add a host alias

1 2

In the OpsCenter console, click Settings > Configuration > Host Alias. From the drop-down list select a host name or type a host name and click Show Alias. All the existing aliases are displayed.

3 4 5

Click Add Alias. Enter the alias name for the host that you have selected from the drop-down list. Click Save.

Settings > Configuration > Host Alias options

A description of the Settings > Configuration > Host Alias options follows in the table. Table 4-8 Option
Select Host

Host Alias options Description

From the drop-down list select a host name or type a host name. Click Show Alias to display the aliases associated with the selected host. A selected host can have one or more alias associated with it. You can clear and save the alias for removing the particular alias.

Show Alias

Alias 1, 2, 3, etc.

Add Alias

Click Add Alias to add aliases for the selected host.

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, backup client, but registered as separate objects (hosts). Using the OpsCenter UI, you can merge only one object into other, at a time. In OpsCenter, you can merge objects (hosts) representing the same backup client. Caution: Object merging is not reversible. To merge two objects

1 2 3

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration > Object merger. Select the Host Type: Master Server, Media Server, or Client. See Settings > Configuration > Object Merger options on page 315.

4 5 6 7

Select the Source Host from the drop-down list. An auto-suggest feature is available. Select the Target Host from the drop-down list. An auto-suggest feature is available. Click Validate Object Merging. You can view the snapshot of the selection that you have made earlier. To modify the Source Host or Target Host click Back. To begin the merge, click Start Merge. Repeat these steps if you want to merge more objects.

Settings > Configuration > Object Merger options

A description of the Settings > Configuration > Object Merger options follows in the table. Table 4-9 Option
Host Type

Object Merger options Description

Select the Media Server, or Client radio button to indicate Host Type.

Note: Object merger for master server is not supported.

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. An auto-suggest feature is available. Source host is the host that you want to merge.

Target Host

Select a target host from the drop-down list. An auto-suggest feature is available. Target host is the host to which you want to merge the source host. Target host is the resultant host after the object merger.

Validate Object Merging

Click Validate Object Merging to view a snapshot of the selection that you have made.

Modifying tape library information in OpsCenter

OpsCenter provides a facility to monitor all the tapes that the data collector uses. Using the OpsCenter UI, you can edit the serial number, manufacturer, alias, slot count of the tape drives the data collector uses. To modify tape library information in OpsCenter

1 2 3 4 5

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration. Click Tape Library. You can view the list of the tape libraries in OpsCenter. Select the check box next to tape library, for which you want to edit the information. Edit the information. See Settings > Configuration > Tape Libary options on page 316.

Click Save.

Settings > Configuration > Tape Libary options

The following table provides a description of the Settings > Configuration > Tape Libary options.

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. Displays the media server to which the tape library is attached. Select the type of tape library from the drop-down list. Enter the serial number of the tape library. Enter the manufacturer of the tape library. Enter the alias for the tape library. Enter the slot count for the tape library.

Host Name

Type Serial Number Manufacturer Alias Slot Count

Copying a user profile in OpsCenter

Most user-definable content, such as reports, cost variables, and cost formulas, is accessible only by the user who has created it. Using the copy user profile functionality, you can copy information from one user account to another. To copy a user profile

1 2 3

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration > Copy User Profile. Select the source user account from the From User drop-down list. See Settings > Configuration > Copy User Profile options on page 318.

4 5 6 7

Select the target user account from the To User drop-down list. In the Copy Items options, select the items you want to copy, for example reports or cost rates and formulae. Click Next. Select reports or cost rates and formulae to be copied to this user profile. If you copy a cost formula, the associated cost variables are implicitly copied. If you copy a cost report, the associated cost formula and variables are implicitly copied.

Click Copy.

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. Table 4-11 Option
From User

Copy User Profile options Description

Select the source user account from the From User drop-down list. Select the target user account from the To User drop-down list. Select the items you want to copy: Reports or Cost Rates and Formulae. Select reports to be copied to this user profile. Select cost rates and formulae to be copied to this user profile. Click Copy to copy the selected items to the selected user profile.

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. Data from exported reports is stored in a default directory, if you have not defined any location. To set report export location

1 2 3 4

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration > Report Export Location. In the Report Export Location box type the directory where you want to save the reports. Click Save.

Settings > Configuration > Report Export Location options

A description of the Settings > Configuration > Report Export Location options follows in the table.

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.

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. See Adding object types in OpsCenter on page 319. See Modifying object types in OpsCenter on page 320. See Deleting object types in OpsCenter on page 320. See Adding attributes to object types in OpsCenter on page 320. See Deleting attributes from object types in OpsCenter on page 321.

Settings > Configuration > Object Type options

A description of the Settings > Configuration > Object Type options follows in the table. Table 4-13 Option
Object Types

Object Type options Description

Click the list box to select an object type that you want to configure. Located to the right of the Object Types drop-down list. Click to add, edit, or delete object types. Located above the Attributes check box. Click to add or delete attributes. Attributes associated with the selected object type.

Add/Edit/Delete

Add/Delete

Attributes

Adding object types in OpsCenter

In OpsCenter you can add or edit attributes of predefined object types. You can also add new object types and attributes for those new object types.

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. In the OpsCenter console, click Settings > Configuration > Object Types. Click Add. Enter the name in the Add Object Type dialog box.. Click OK.

Deleting object types in OpsCenter

You can only delete an object type that you have created. You cannot delete the predefined objects in the drop-down list. To delete object types

1 2 3 4

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration > Object Types. Select the object type from the drop-down list. You can delete the object types that you have created. You cannot delete predefined object types. Click Delete.

See Adding object types in OpsCenter on page 319.

Modifying object types in OpsCenter

You can only modify the name of an object type that you have created. You cannot modify the name of the predefined objects in the drop-down list. To modify an object type name

1 2 3

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration > Object Type. Select the object type that you want to modify from the drop-down list. You can rename the object types that you have created. You cannot rename the predefined object types.

4 5

Click Add. In the Add Object type dialog, type a name for the object type and click OK.

Adding attributes to object types in OpsCenter

You can add attributes to all object types.

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. In the OpsCenter console, click Settings > Configuration > Object Types. Select the object type from the drop-down list and in Attributes section, click Add. Enter the name of the attribute and click OK.

See Adding object types in OpsCenter on page 319.

Deleting attributes from object types in OpsCenter

You can delete the attributes that are added to an object type. To delete attributes from an object type

1 2 3 4

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Configuration > Object Types. Select the object type from the drop-down list. In the Attributes section, select the check box in front of the attribute you want to delete. Click Delete.

About managing Symantec OpsCenter users

After you install Symantec OpsCenter, you need to create user accounts. The Symantec Product Authentication Service validates credentials of OpsCenter users based on Windows, NIS, or private domains. See User access rights and UI functions in OpsCenter on page 322. See Adding new users to OpsCenter on page 327. See Resetting a OpsCenter user password on page 328. See Adding OpsCenter user groups on page 329. See Viewing OpsCenter user account information on page 326. See Adding new users to OpsCenter on page 327. See Editing OpsCenter user information on page 327. See Resetting a OpsCenter user password on page 328. See Deleting OpsCenter users on page 328.

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. Table 4-14 Option
Add/Edit/Delete options Name Email address User Role

Users options Description

Click Add/Edit/Delete to add, edit, or delete users. Login name of the user. Email address that you provided while adding the user. Role that is associated with the user. See User access rights and UI functions in OpsCenter on page 322.

Domain Type

Domain type (like vx) that the user is a member of and also specified while adding the user. Domain name (like OpsCenterUsers) that the user is a member of and also specified while adding the user .

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. Table 4-15 provides details of the OpsCenter UI functions that you can perform. Table 4-15 OpsCenter UI functions

OpsCenterfunctions Tasks
User Management The User Management function includes the following tasks:

Create, update, delete users. Create, update, delete user groups. Add, remove users from user groups. Assign, remove roles to users and user groups.

OpsCenterManagement The OpsCenter Management function includes the following tasks:

Add, Update, Delete Master Server Add, Update, Delete OpsCenter Agents Set default currency, SNMP, SMTP server

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, update, delete NetBackup entities: Host Properties, Policy, Media and Devices, and others

NetBackup Operations The NetBackup Operations function includes the following tasks: Change states of the NetBackup entities as follows:

Policy (Activate/De-active) Job (Stop/Start/Suspend/Resume) Media (Assign, Freeze, unfreeze ) Drives (Up/Down) Others

Backup and Recovery

The Backup and the Recovery function includes the following tasks:

Execute manual backups. Search and restore files, folders, application (Oracle, SQL Server, and Exchange Server)

Views Management

The Views Management function includes the following tasks:

Create, update, delete OpsCenter views and nodes. Assign Read / Write permissions to users on OpsCenter views and nodes.

All Views Read

The NetBackup Operations function includes the following tasks:

View OpsCenter views and nodes.

Report Execution

This function includes the following tasks:

Execute report templates and public custom reports. Schedule canned and public custom reports. Create, update Dashboard.

Custom Reports

This function includes the following tasks:

Create, update, delete custom reports. Make custom reports public, private, or both.

Custom SQL Reports

This function includes the following tasks:

Create, update, delete custom SQL reports.

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, Summary, Details): Job, Policy, Media, Alerts, Drives, Others.

Alert Management

The Alert Management function includes the following tasks:

.Create, update, delete alert policies. Assign, acknowledge, clear alerts.

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. The OpsCenter Security Administrator can create, edit, or delete users.

Note: An Administrator in VBR (Veritas Backup Reporter)

or NOM (NetBackup Operations Manager) is a Security Administrator in OpsCenter. Administrator This user can perform all OpsCenter functions except for user management. The OpsCenter Administrator cannot create, edit, or delete users.

Note: A NOM user becomes an Administrator in OpsCenter.

Operator This user is not involved in the activities that are related to managing users, OpsCenter Server, and NetBackup configuration.

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. This user cannot perform functions, such as user management or backup & recovery. The Analyst has the Read permission on all views.

Note: A NOM read-only user becomes an Analyst in

OpsCenter. A VBR read-only admin becomes an Analyst in OpsCenter. Reporter The role of this user is to mainly generate the operational and business-level reports for further analysis.

Note: A VBR user becomes a Reporter in OpsCenter.

Note: From 7.1 onwards, a reporter and analyst would be able to view only those schedules that they themselves create. The Security Administrator, Administrator, and Operator would however be able to access all the schedules. A reporter would now have access to all the master servers, irrespective of the access permissions. Table 4-17 lists the OpsCenter user roles and the OpsCenter UI functions that these users can perform. 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

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

Restricted to only permitted entities Y

Y Y

Y Y

Y Y

Y Y

Y Y

Y represents Yes, which means that the users of this role can perform this particular OpsCenter function. N represents No, which means that the users of this role cannot perform this particular OpsCenter function. See About managing Symantec OpsCenter users on page 321.

Viewing OpsCenter user account information

You can view a list of OpsCenter users and their information such as, name, user name, access level, authentication domain, and so on. The user information is arranged in a tabular format. You can sort the table by user attributes. To view OpsCenter user account information

1 2 3

Log on to the OpsCenter console with administrator privileges. In the Symantec OpsCenter console, click Settings > Users. Click Users to view the list of users.

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. To add a new user to OpsCenter

1 2 3 4 5

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. On the Users tab, click Add. Select the user creation type: New User or Existing Domain User. Enter the following general and demographic details of the user: User name, user role, domain name, email ID, first name, last name, department, cost center, work number, mobile number, and contact details. The following user information is mandatory: User Name, Password, Confirm Password, and User Role See User access rights and UI functions in OpsCenter on page 322. If you have selected the Existing Domain User option, you do not have to enter Password and Confirm Password. If you have selected the New User option, specify the password, and enter it once again for confirmation.

Click Save.

Editing OpsCenter user information

You can edit the existing users. To edit an existing user in OpsCenter

1 2 3 4

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. On the Users tab, click the check box in front of the user that you want to edit. Click Edit.

328

Understanding OpsCenter settings About managing Symantec OpsCenter users

Modify the user information. You cannot modify the domain of the user. You can also reset passwords of the OpsCenter users using this page. See Resetting a OpsCenter user password on page 328.

Click Save.

Resetting a OpsCenter user password

This section describes how to reset a user password. The Reset Password functionality is applicable only for OpsCenter users. To reset a user password

1 2 3 4 5 6 7

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. On the Users tab, click the check box in front of the user for whom you want to reset the password. Click Edit. In the General Details pane, click Reset Password. On the Reset Password page, enter the new password and confirm password for the selected user. Click Save.

See About managing Symantec OpsCenter users on page 321.

Deleting OpsCenter users

You can delete the user accounts that do not need to be maintained. Note: The default OpsCenter user admin cannot be deleted.

Warning: Do not inadvertently delete all your administrator accounts. To delete a OpsCenter user

1 2 3

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. Click Users.

Understanding OpsCenter settings About managing Symantec OpsCenter users

329

4 5

Check the box next to the user account you want to delete. Click Delete.

Viewing OpsCenter user groups

This section provides the procedure to view the existing user groups. To view a user group

1 2 3

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. Click User Groups to view the list of user groups.

Settings > Users > User Groups options

A description of the Settings > Users > User Groups options follows in the table. Table 4-18 Option
Add/Edit/Delete options

User Groups options Description

Click Add to add user groups. Click Edit to add or delete users to the existing user group. Click Delete to delete the user groups. Enter a name for the user group that you add. Enter a description for the user group that you add.

Name Description

Adding OpsCenter user groups

If you want to give the same privileges to multiple users, add them to a single user group. The same access rights on views are attributed to all users in the user group . To create an OpsCenter user group

1 2 3 4 5 6

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. Click User Groups. Click Add. On the User Groups tab, enter the name of the group and description. In the List of Users pane, click Add to open the Add Users pop-up screen.

330

Understanding OpsCenter settings About managing recipients in OpsCenter

7 8 9

On the Add Users dialog box, select the users that you want to add to this user group. Click OK. On the User Group tab, click Save.

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. In the OpsCenter console, click Settings > Users. Click User Groups . Select the check box in front of the user group that you want to edit. Click Edit. Modify the user group name or description. Add or delete the users using the List of Users pane and Add Users pop-up screen. Click Save.

Deleting OpsCenter user groups

You can delete a user group that you no longer need. To delete a Symantec OpsCenter user group

1 2 3 4 5

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Users. Click User Groups. Select the check box next to the user groups that you want to delete. Click Delete.

About managing recipients in OpsCenter

You can specify the recipients to whom you want to send alert notifications or email reports.

Understanding OpsCenter settings About managing recipients in OpsCenter

331

Note: Make sure that the mail server is configured to send emails. See Configuring SMTP server settings for OpsCenter on page 311. The following sections provide procedures for viewing, creating, modifying, and deleting email and SNMP trap recipient information. See Viewing email recipients in OpsCenter on page 331. See Viewing SNMP trap recipients in OpsCenter on page 332. See Creating OpsCenter email recipients on page 333. See Creating OpsCenter SNMP trap recipients on page 334. See Modifying OpsCenter Email or SNMP recipient information on page 336. See Deleting OpsCenter Email or SNMP trap recipient on page 336.

Viewing email recipients in OpsCenter

This section provides the procedure to view the available email recipients. To view the email recipients

1 2

Log on to the OpsCenter console. In the OpsCenter console, click Settings > Recipients. By default, the Email tab is selected. All email recipients are displayed on this tab.

Modify recipients and recipient details as needed.

See Settings > Recipients > Email options on page 331. See About managing recipients in OpsCenter on page 330.

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

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, it is not available for selection on the Adding Email Recipients pop-up screen, when emails are sent.

Description

Description about the email recipient

Viewing SNMP trap recipients in OpsCenter

This section provides the procedure to view the available SNMP trap recipients. To view the SNMP trap recipients

1 2 3 4

Log on to the OpsCenter console. In the OpsCenter console, click Settings > Recipients. Click SNMP. 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. Table 4-20 Option
Recipient Name SNMP Host Port

SNMP trap recipient options Description

Name of the SNMP trap recipient. Name of the SNMP host. Port number on the SNMP host where you want to send traps. The status of the trap recipient that states whether it is active or not. If a recipient is not active, it is not available for selection on the Adding Trap Recipients pop-up screen, when alert policies are configured.

Active

Description

Description about the trap recipient.

Understanding OpsCenter settings About managing recipients in OpsCenter

333

Creating OpsCenter email recipients

This section describes how to create email recipients. To create email recipients

1 2 3 4

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Recipients. In the Email tab, click Add to create new email recipients. Enter the required information. See Settings > Recipients > Email > Add Email Recipient options on page 333.

Click Save.

Settings > Recipients > Email > Add Email Recipient options
A description of the Settings > Recipients > Email > Add Email Recipient options follows in the table. 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. Enter the email ID of the official, to which alert notifications or reports are sent. Select this check box if you want the recipient to receive alert notifications and reports by emails. Enter a short description about the alert or report so that recipients can understand. Select this check box to activate the Alert Notification Delivery Limit settings. If you do not select this check box, Maximum Number of Messages, Delivery Time Span, and Reset Message Count After Time are not taken into account when notifications are sent. Enter the maximum number of notifications that you want to receive within the specified Delivery Time Span.

Email Address

Active

Description

Activate Delivery Limit

Maximum Number of Messages

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, minutes, or seconds, during which notifications are sent. Once the message count reaches Maximum Number of Messages, the Notification Manager blocks the delivery of any new notifications to the associated recipient for the time period that is specified for Reset Message Count After Time.

Delivery Time Span

Reset Message Count After Enter the time period in hours, minutes, or seconds, during Time which notifications are blocked if the message count has reached Maximum Number of Messages. Once this time period is over, Maximum Number of Messages is reset and the Notification Manager starts sending notifications for the specified Delivery Time Span.

Note: For example, assume Maximum Number of Messages

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

Creating OpsCenter SNMP trap recipients

Traps or interrupts are signals sent to inform the programs that an event has occurred. In OpsCenter, traps are the notifications that are sent to a specified SNMP host or group of hosts when a condition is met. A trap recipient is a host that receives notifications in the form of SNMP traps when an alert condition is met. For example, a trap is sent after an alert was generated as a result of failure of communication between the OpsCenter Agent and Server. For more details, refer to the About using SNMP with OpsCenter section. To create SNMP recipients

1 2 3 4

Log on to the OpsCenter Server host with administrator privileges. In the OpsCenter console, click Settings > Recipients. Click SNMP. Click Add.

Understanding OpsCenter settings About managing recipients in OpsCenter

335

In the SNMP Attributes page enter the required information. See Settings > Recipients > SNMP > Add SNMP trap recipient options on page 335.

Click Save.

Settings > Recipients > SNMP > Add SNMP trap recipient options
A description of the Settings > Recipients > SNMP > Add SNMP trap recipient options follows in the table. Table 4-22 Option
Recipient Name SNMP Host SNMP Port

Add SNMP trap recipient options Description

Enter the name of the SNMP trap recipient. Enter an SNMP host, to which you want to send traps. Enter the port number on the SNMP host where you want to send traps. Select this check box if you want the recipient to receive notifications by SNMP traps. Enter a short description about the traps. Select this check box to activate the Alert Notification Delivery Limit Settings. If you do not select this check box, Maximum Number of Messages, Delivery Time Span, and Reset Message Count After Time are not taken into account when notifications are sent. The notifications are sent as soon as alerts are generated. Enter a maximum number of notifications that can be sent within the specified Delivery Time Span. Enter the time duration in hours, minutes, or seconds, during which notifications are sent. Once the message count reaches Maximum Number of Messages, Alert Manager blocks the delivery of any new notifications to the associated recipient for the time period that is specified for Reset Message Count After Time.

Active

Description Activate Delivery Limit

Maximum Number of Messages Delivery Time Span

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, minutes, or seconds, during Time which notifications are blocked if the message count has reached Maximum Number of Messages. Once this time period is over, Maximum Number of Messages is reset and Alert Manager starts sending notifications for the specified Delivery Time Span.

Modifying OpsCenter Email or SNMP recipient information

Only OpsCenter administrators can modify email or trap recipient information. See Creating OpsCenter email recipients on page 333. See Creating OpsCenter SNMP trap recipients on page 334. To modify email or SNMP trap recipient information

1 2 3 4 5

In the OpsCenter console, click Settings > Recipients. In the Email Recipients tab or SNMP Recipients tab, select the email or trap recipient that you want to edit. Click Edit. On the modify email or trap recipient page, change Email Recipient or SNMP Trap Recipient attributes and Alert Notification Delivery Limit Settings. Click Save.

Deleting OpsCenter Email or SNMP trap recipient

Only OpsCenter administrator can delete email or trap recipient. See Creating OpsCenter email recipients on page 333. To delete Email or SNMP trap recipient

1 2 3 4

In the OpsCenter console, click Settings > Recipients. In the Email Recipients tab or SNMP Recipients tab, select the email or trap recipient(s) from the table that you want to delete. Click Delete. Click Save.

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. In OpsCenter Analytics, you can choose the currency that you want to be displayed on cost reports. If you have OpsCenter administrator privilege, you can set multiple global currencies, one of which can be set as default currency. You can set the cost variable, cost formulae, and cost estimation that you want to run the cost reports. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. This feature is disabled for unlicensed OpsCenter version. The following sections provide procedures for managing cost analysis and chargeback. See Setting the default currency for OpsCenter cost reports on page 337. See Editing the OpsCenter global currency list on page 338. See Settings > Chargeback > Cost Variable options on page 339. See Settings > Chargeback > Cost Formulae options on page 343.

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. Note: Setting the default currency gives you the flexibility of displaying cost report values in the currency of your choice. However, OpsCenter does not support conversion of currencies. To set the default currency for cost reports

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. This feature is disabled for unlicensed OpsCenter version.

On the Currency Settings tab, in the Default Currency drop-down list, all global currencies that are set by the administrator are available for selection. Select a currency from the drop-down list. See Editing the OpsCenter global currency list on page 338.

338

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics

Select the Currency Display Mode: Currency Code or Currency Symbol. For example, for US dollar currency you can either select a currency code USD or symbol $, which appears on chargeback reports. Select the Display Currency Option in Cost Reports check box to show the default currency on the cost reports. Click Save.

5 6

Settings > Chargeback > Currency Settings options

A description of the Settings > Chargeback > Currency Settings options follows in the table. Table 4-23 Option
Default Currency

Currency Settings options Description

Select a currency from the drop-down list. All global currencies that are set by the administrator are available for selection. Click this option to change the list of currencies available for selection. Select the Currency Display Mode: Currency Code or Currency Symbol. For example, for US dollar currency you can either select a currency code USD or symbol $, which appears on chargeback reports.

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.

Editing the OpsCenter global currency list

This section provides the procedure to edit the global currency list. This list is available when a default currency is selected to be displayed on OpsCenter cost reports. To edit the global currency list

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. If you have not entered the Symantec OpsCenter Analytics license key, you cannot access the Settings > Chargeback feature. This feature is disabled for unlicensed OpsCenter version.

On the Currency Settings tab, click Edit Currency List.

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics

339

On the Edit Currency List pop-up screen, select currencies from the Global Currency list which you want to make available for selection in the Currency Settings > Default Currency drop-down list. See Setting the default currency for OpsCenter cost reports on page 337.

Click Add to add the selected currencies to the User Currency list. You can use Add, Remove, Add All, and Remove All options to alter the User Currency list.

Click OK.

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. It is the default currency list and lists the currencies that you select. You can use these options to alter the User Currency list.

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. 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. Displays the metric that you select for the cost variable.

Total Date Ranges and Rates Displays the date ranges and rate in units for the date range that you select.

340

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics

And if you click the Add option, a page with the following settings appears. 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. Select a variable metric from the drop-down list for the cost variable that you add. Measure costs for a specific type of job, for example Backup or Restore. The default option is All. Measure costs for the jobs that use a specific policy type. In NetBackup, the policy type determines the type of clients that can be part of the policy and, in some cases, the types of backups that can be performed on the clients. Examples include DB2, Sybase, and MS Exchange Server. The default policy type is All. Measure cost for a specific transport type for example, LAN (local area network) or SAN (storage area network ). The default option is All. Measure cost for a specific storage type for example, tape or disk. OpsCenter supports NetBackup's disk-based data protection feature, which enables you to select disk as a storage type, when a cost variable is created. The default option is All. Select to add a start date to the cost variable. Select to add a end date to the cost variable. You can also select Never as the end date. Add an associated rate to the cost variable. Select to add more date ranges.

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. Typically, each service is represented by one variable that reflects the cost of the service, for example $1.00 per backup job. However, you can account for rate changes in one of two ways: by creating two variables for the same service (which you can include in a single cost formula later) or by incorporating both rates into

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics

341

a single variable. For example, a single variable can incorporate the rate of $1.00 per backup job until 31 December 2004 and the rate of $1.25 per backup job starting on 1 January 2005. Note: To generate deduplication savings reports, you must create a cost variable with the Protected Job Size (GB) metric. To set up OpsCenter to run cost reports, you need to create the variables that define the cost of various services. To create a cost variable

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Variable.

3 4 5

On the Cost Variable tab, click Add. Enter the variable name. Select any of the following variable metrics from the drop-down list:

Daily Occupancy Job Count Job Size Protected Job Size

If necessary, select additional parameters to refine the metric you selected. For Job Count, Job Size, and Protected Job Size select the Job Type, Job Policy Type, Job Transport Type, and Job Storage Type. Note: These fields are not applicable for the Daily Occupancy variable metric. See Settings > Chargeback > Cost Variable options on page 339.

Add one or more date ranges using the drop-down lists for Month, Day, Year, and Time. Add an associated rate by typing a cost per service unit (such as backup jobs or backed-up GB) in the Rate field. Add at least one date range.

342

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics

Optionally, to add more date ranges, click Add New Range. This can be useful for defining multiple date ranges to represent historical or future changes in service costs. You can also modify the variable later to add or delete date ranges as costs change.

Click OK . You can now use the variable you created to build the formulas that form the basis for cost reports. See Creating cost formulae 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. For example, you can modify the name, date ranges and rates of a variable to reflect changing conditions in your enterprise. To modify a cost variable

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Variables.

3 4 5 6

Select the check box in front of the variable name that you want to modify. Click Edit. Modify the cost variable details. Click OK.

Deleting cost variables in OpsCenter

You can variables you no longer need. Deleting a cost variable removes it permanently from the database, and you must update any formulas that use the variable. To restore a deleted variable, you must recreate the variable manually. To delete a cost variable

1 2 3 4 5

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Variables. Select the check box in front of the cost variable that you want to delete. Click Delete.

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. 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. Displays the number of cost variables added to the cost formulae.

Creating cost formulae in OpsCenter

After you create cost variables, create the formula that define the cost of various services to run cost reports. To create a cost formula

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Formulae.

3 4 5

On the Cost Formulae tab, click Add. Enter the name of the formula. Select a cost variable from the drop-down list. You need to select at least one cost variable.

Optionally, to define formulae containing more than one variable, click Add new cost variable. Select a different variable from the drop-down list. You can also modify the formulae later to add or delete variables.

Click OK. You now can use the formula to create cost reports. These reports help you evaluate the cost of services and make decisions about what to charge for performing those services.

Modifying cost formulae in OpsCenter

You can modify the name and variables of a cost formula that you have created.

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. For example, you might want to update a formula that is called RecoveryRate to reflect a change in the hourly rate that is charged for recovery operations. To modify a cost formulae

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Formulae.

3 4 5 6

On the Cost Formulae tab, select the cost formulae that you want to modify. Click Edit. Modify the details of the cost formula. Click OK.

Deleting a cost formulae in OpsCenter

You can also delete formulae that you no longer need. Deleting a cost formula removes it permanently from the database. To delete cost formulae

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Formulae.

3 4 5

On the Cost Formulae tab, select the cost formulae that you want to delete. Click Delete. On the confirmation dialog box, click OK.

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. Using historical data, it provides you with an estimate of how much it costs your organization to provide a specific kind of service. For example, suppose you anticipate spending $500,000 over the next year to provide backup services throughout your enterprise. By inserting the metric Daily Occupancy into the tool, along with the amount $500,000, you can obtain an estimate per kilobyte that is based on the backup activity you performed last year. See Creating cost variables in OpsCenter on page 340.

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics

345

See Creating cost formulae in OpsCenter on page 343. To estimate baseline (chargeback) costs using the Formula Modeling Tool

1 2

Log on to the OpsCenter console with administrator privileges. In the OpsCenter console, click Settings > Chargeback. Click Cost Estimation.

3 4

Select a Report Grouping parameter to define the models scope. Use the Metric Selection parameters to specify the metric whose rate you want to estimate: See Settings > Chargeback > Cost Estimation options on page 345.

5 6

Use the following Time Frame parameters to define the time intervals for which data is modeled. Click Run Model to input different values into the model, or to run a new model.

Settings > Chargeback > Cost Estimation options

A description of the Settings > Chargeback > Cost Estimation options follows in the table. Table 4-28 Option
Report Grouping

Cost Estimation options Description

Select a report grouping parameter to define the model's scope. Examples: All Master Servers or User

Metric

Select a metric or category of service. Example: Daily Occupancy

Amount

Specify the total amount of money, in dollars, you expect to charge for service within that category in a given time frame. Examples: $50000, $10000, or $10000.00

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. You can choose either absolute or relative dates. Choose absolute dates if you want the estimates contents to remain static whenever you display it. Choose relative dates if you want the estimate to reflect data that was collected over the most recent time interval. Select one of the following: Click Absolute to configure an absolute time frame. Select a start time (month, day, year, and time of day) using the From drop-down lists, and a stop time using the To drop-down lists. The estimate reflects data from the time period between the start and the end dates. Example: From MAR 1 2004 12:00 A.M. to APR 30 2004 12:00 A.M. Click Relative to configure a relative time frame. Then select a time interval using the Last drop-down lists. The estimate reflects the data that is collected within the specified time period, up to the current time.

Examples: Last 21 Days or Last two Quarters The Relative setting is especially useful for the estimates that you plan to generate on a regular basis. Such estimates always reflect the data that is collected over the most recent time interval.

Chapter

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.

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. Symantec NetBackup PureDisk Symantec Enterprise Vault (Windows only) Note: To collect archive data from Enterprise Vault, you need to install the OpsCenter Agent on a Windows host. IBM Tivoli Storage Manager (TSM) EMC NetWorker

See About configuring data collection for NetBackup on page 361. See About OpsCenter Agents on page 348. See OpsCenter Data Collector types on page 349. See Backup and archiving products supported by Symantec OpsCenter 7.1 on page 351.

About OpsCenter Agents

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

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. By default the InstallPath is: C:\Program Files Naming convention for the OpsCenter Agent log file:
5*-146-*.log

An example of the OpsCenter Agent log file name:

58330-146-2567491850-091129-0000000000.log

OpsCenter Data Collector types

The OpsCenter data collectors, collect data from backup and archiving product hosts. Each data collector collects data from a single product host. You can configure multiple data collectors on a single OpsCenter Agent host. You can create data collectors to communicate with the various products, such as Backup Exec, Enterprise Vault, or EMC NetWorker. These data collectors collect the specified data type as specified in the configuration. You can specify to collect all or some of the data types for that product. For example, Backup Exec data collector can collect Tape Drive Usage, Media, Policy and Schedule, Job, or Image. Note: Error logs and skipped files are collected as part of job data. You can enable or disable a data collector. Table 5-1 lists the data collectors that you can configure in OpsCenter. Table 5-1 Data collector types Description

Data Collector type

Symantec Backup Exec Data Create this data collector to collect data from Backup Exec. Collector (Windows only) See Configuring Backup Exec data collector on page 388.

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. See Collecting data from PureDisk on page 389.

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. To collect PureDisk data, you need to create a data collector for the Integrated Agent. 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. Create this data collector to collect data from TSM. See IBM Tivoli Storage Manager data collector variables and details on page 405. EMC NetWorker Data Collector Create this data collector to collect data from EMC NetWorker. See EMC NetWorker data collector variables on page 406.

TSM Data Collector

Table 5-2 lists the data types that are collected by OpsCenter 7.1 from various backup and archiving products. Table 5-2 Data Types Data types collected NetBackup Backup Enterprise Vault Exec Symantec IBM EMC NetBackup Tivoli NetWorker PureDisk Storage Manager
(6.2.x, 6.5.x, (5.3, 5.4, 6.6, 6.6.0.1, 5.5) 6.6.0.2, 6.6.0.3) 7.3

(6.0MP7, 6.5, 6.5.2A, 6.5.4, 6.5.5, 7.0, 7.0.1, 7.1) Job Y

(10.x, 11.x, 12.x, 2010)

7.5

8.0

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

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. Note that with the licensed version of OpsCenter, you can do advanced reporting from the data that is collected from all of these products. With the unlicensed version, you cannot collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC NetWorker. Table 5-3 lists the backup and archiving products that OpsCenter supports.

352

Understanding data collection About data collection in OpsCenter

Table 5-3

Backup and archiving products supported by Symantec OpsCenter 7.1 Versions

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

Backup or Archiving product

Symantec NetBackup

Support level
All supported NetBackup platforms (except 7.1) by remote agent

Note: NBU 7.1 does not require any

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

Symantec NetBackup PureDisk

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

PureDisk supported platform (PDOS) by the OpsCenter integrated Agent. You do not need a separate Agent to collect data from PureDisk. You can use the inbuilt Agent of the OpsCenter Server for data collection. To create or configure the data collector, select the Agent that is installed as Integrated Agent.

Symantec Backup Exec

10d, 11d, 12.0, 12.5, 2010, All supported Symantec Backup 2010 R2 Exec platforms by remote agent.

Note: OpsCenter does not Native agent on backup servers on

support Symantec Backup Windows 2003 (SP2 & R2), 2008 Exec running on NetWare. (SP2 & R2) Symantec Enterprise Vault 7.5, 8.0 All supported Symantec Enterprise Vault platforms by remote agent Native agent on Microsoft SQL Server 2005 or 2008 (where Enterprise Vault database resides) on Windows 2003 (SP2 & R2), 2008 (SP2 & R2). EMC NetWorker 7.3 Native agent on backup servers on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.

Understanding data collection About managing OpsCenter Agents

353

Table 5-3

Backup and archiving products supported by Symantec OpsCenter 7.1 (continued) Versions
5.3, 5.4, 5.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), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.

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. A backup or archive product host means a supported product host that is connected to OpsCenter. Examples of a backup or archive product host (product host) are PureDisk host, Backup Exec host, NetBackup master server, Enterprise Vault host etc. If the OpsCenter server and the product host are in the same time zone (like CST), both OpsCenter server and the product host must show the same time. For example, if the OpsCenter server and the product host are in CST time zone, but show different time like 8 pm and 10 pm, then OpsCenter may not display accurate data in the reports and also Monitor and Manage tabs of the OpsCenter console. If the OpsCenter server and product host are in different time zones like CST and PST, then ensure that both the CST and the PST time convert to the same GMT time. For example if the OpsCenter server and the managed host show 8 pm CST and 9 pm PST respectively, then 8 pm (CST) and 9 pm (PST) must translate to the same GMT time.

About managing OpsCenter Agents

The following topics provide more information about viewing, modifying, creating, and deleting an OpsCenter Agent configuration. See About the OpsCenter Agent on page 35. See Viewing OpsCenter Agent status on page 355. See Configuring an OpsCenter Agent on page 355. See Modifying an OpsCenter Agent on page 356.

354

Understanding data collection About managing OpsCenter Agents

See Deleting OpsCenter Agents on page 357.

Settings > Configuration > Agent options

A description of the Settings > Configuration > Agent options follows in the table. 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. Select Delete Agent to delete the selected agent. See Settings > Configuration > Agent > Create Agent or Edit Agent options on page 356.

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. Select Delete Data Collector to delete the selected agent. See Data Collector Wizard settings on page 359.

Name Product Host

Name of the Agent host. Host from where data is collected by the Agent like Backup Exec server , PureDisk server etc. Data collection status for policy and schedule on the product host. Data collection status for tapes on the product host. Data collection status for media on the product host. Data collection status for jobs on the product host. This field is specific to Enterprise Vault hosts. This field is specific to Enterprise Vault hosts. This field is specific to EMC NetWorker. This field is specific to Enterprise Vault hosts.

Policy and Schedule

Tape Drive Information

Media

Job Archive Archive Policy Images Target

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.

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. To view Agent status

1 2

In the OpsCenter console, click Settings > Configuration > Agent. On the Agent list, select an Agent to view its status at the bottom of the page. By default the General tab is selected. The tab displays the parameters which you have specified when you created this Agent. See Settings > Configuration > Agent options on page 354. See Configuring an OpsCenter Agent on page 355.

Click the Agent Summary by Data Collector Status, Agent Summary by Data Type Status, or Agent Summary by Data Collector Count tab to view the relevant details.

Configuring an OpsCenter Agent

This section provides the procedure to configure an OpsCenter Agent.

356

Understanding data collection About managing OpsCenter Agents

To configure an OpsCenter Agent

1 2

In the OpsCenter console, click Settings > Configuration > Agent. Click Create Agent and complete the fields. See Settings > Configuration > Agent > Create Agent or Edit Agent options on page 356.

Click Save.

Settings > Configuration > Agent > Create Agent or Edit Agent options
To create an Agent, 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. For example: Solaris Family or Windows Family For Windows hosts, you can configure an Agent for all supported backup and archiving products. For Solaris hosts, 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. To modify an OpsCenter Agent

1 2 3

In the OpsCenter console, click Settings > Configuration > Agent. From the list of agents, select the check box in front of the Agent that you want to modify. Click Edit Agent.

Understanding data collection About managing OpsCenter Data Collectors

357

4 5

On the Edit Agent page, modify PBX port or OpsCenter Server Network Address. Click Save.

Deleting OpsCenter Agents

This section provides the procedure to delete an OpsCenter Agent. To delete an OpsCenter Agent

1 2 3

In the OpsCenter console, click Settings > Configuration > Agent. From the list of agents, select the check box in front of the Agent that you want to delete. Click Delete.

About managing OpsCenter Data Collectors

The following topics provide more information about viewing, configuring, modifying, or deleting a data collector. See Viewing OpsCenter Data Collector status on page 357. See Configuring an OpsCenter Data Collector on page 358. See Modifying an OpsCenter Data Collector configuration on page 360. See Deleting OpsCenter Data Collectors on page 361.

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. To view data collector status

1 2

In the OpsCenter console, click Settings > Configuration > Agent. On the Agent list, expand an Agent to view the Data Collectors that are configured for this Agent.

358

Understanding data collection About managing OpsCenter Data Collectors

Select a Data Collector to view its details and status at the bottom of the page. By default the General tab is selected displaying the following Data Collector details, which you have specified when you created this Data Collector. See Configuring an OpsCenter Data Collector on page 358.
Product Displays the name of the product type, for which this Data Collector is configured. For example: Symantec Backup Exec Product Host Status Displays the name of the target host, which this Data Collector collects data from. Displays the status of the Data Collector as Enabled or Disabled that you have set. If the Data Collector status is disabled, the data is not collected from the target host.

Select the Data Collection Status tab. There is more information about the parameters displayed on this tab. See Data collection status of a master server on page 373.

Configuring an OpsCenter Data Collector

OpsCenter is designed to provide extensive reporting on the data that is received from backup and archiving products. OpsCenter consists of Server, Agent, Java View Builder, and a console. The OpsCenter Agent contains product-specific data collectors collecting data from the products and returning it to the OpsCenter Server. You can generate various business reports on this backup data or archiving data. After you install and configure an OpsCenter Agent, configure the data collectors. See Configuring an OpsCenter Agent on page 355. To configure a data collector

1 2 3 4

In the OpsCenter console, click Settings > Configuration > Agent. On the Agent list, select a check box in front of the Agent, for which you want to configure a Data Collector. Click Create Data Collector. Complete the fields on the Create Data Collector: Product Selection page.

Understanding data collection About managing OpsCenter Data Collectors

359

Click Next. On the Create Data Collector: Details page, the Target Details, Configuration Settings, and Data Collection details are displayed.

Verify or modify the default Target Details: See Data Collector Wizard settings on page 359.

Enter the data collector ConfigurationSettings. These settings vary depending on the data collector type you configure. For product specific configuration settings, refer to the respective data collector settings. See Configuring Backup Exec data collector on page 388. See About collecting data from Enterprise Vault on page 392. See IBM Tivoli Storage Manager data collector variables and details on page 405. See EMC NetWorker data collector variables on page 406.

8 9

Enter the Data Collection Settings. Click Save.

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. For example, Symantec Backup Exec. The options available in the Select Product drop-down list depends on the Agent operating system family that you have selected while creating the respective Agent.

Target host name

Enter the name of the product host from which you want to collect backup or archiving data.

Complete the Data Collector: Details fields as follows:

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. You need to specify the product name when you create the data collector. For example: Symantec Backup Exec. Displays the name of the product host from which this data collector collects data. You need to specify the product name when you create the data collector. By default, the data collector status is Enabled. You can disable the data collection by changing the status.

Target host name

Data Collector Status

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

Configuration Status Collectible Data Type

Modifying an OpsCenter Data Collector configuration

This section provides procedure to modify configuration of a Data Collector.

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. In the OpsCenter console, click Settings > Configuration > Agent.. On the Agent list, expand an Agent to view Data Collectors that are configured for this Agent. Select a check box in front of the Data Collector that you want to modify. Click Edit Data Collector. On the Edit Data Collector: Details page, modify the Target Details. Modify data collection configuration settings. These settings vary depending on the product, which this data collector collects data from. Modify blackout period settings. Modify collection interval.

10 Click Save.

Deleting OpsCenter Data Collectors

This section provides procedure for deleting Data Collector configurations from an Agent. To delete a Data Collector configuration

1 2 3 4 5

Log on to the OpsCenter Server. In the OpsCenter console, click Settings > Configuration > Agent. On the Agent list, expand an Agent to view Data Collectors that are configured for this Agent. Select check boxes in front of the Data Collectors that you want to delete. Click Delete Data Collector.

About configuring data collection for NetBackup

This section describes how OpsCenter collects data from NetBackup. It also describes how you can add, edit, delete, and control data collection for a master server. The following sections describe the NetBackup data collection in detail:

NetBackup data collection view How OpsCenter collects data from NetBackup

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. Table 5-9 Option
Add/Edit/Delete

NetBackup options Description

Select Add to add a NetBackup master server to the OpsCenter console. Note that you must first configure the master server to allow server access and data collection by OpsCenter. After configuring the master server, you must add this server to the OpsCenter console so that it can be monitored. See Adding a master server in OpsCenter on page 377. Select Edit to edit the properties of a master server. The Network Name of a master server cannot be edited. Select Delete to delete one or more master servers from the OpsCenter console. Deleting a master server removes all the data that is associated with the master server from the OpsCenter database.

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. Name or IP address of the master server that is configured. The display name that you have chosen for the master server. Operating system of the master server. Backup product and version from where the data is collected.

Network Name Display Name

Operating System Product

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

NetBackup data collection view

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

Display Name

Operating System Product

Last Contact

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.

How OpsCenter collects data from NetBackup

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

Understanding data collection About configuring data collection for NetBackup

365

Note: A NetBackup 7.1 master server does not require any OpsCenter Agent or data collector for data collection. For 7.0.x master servers, an Agent must be installed only if you want to collect breakup jobs data. For 6.5.x master servers, an Agent must be installed only if you want to collect specific data (image, error log, scheduled jobs, and breakup jobs data). For 6.0 MP7 master server, you cannot collect scheduled jobs and breakup jobs data. Hence for a 6.0 MP7 master server, an Agent must be installed only if you want to collect image data and error logs data. The OpsCenter server software collects data from NBSL in the following ways:

Initial data load Listening for change notifications

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

366

Understanding data collection About configuring data collection for NetBackup

port on the NetBackup master server, you can configure the same in OpsCenter while adding or editing a master server.

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. The Breakup Jobs functionality was earlier available in Veritas Backup Reporter (VBR). With the Breakup Jobs option, 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. The Breakup Jobs functionality is most effective if you have multiple backup selection lists in the NetBackup policy. You can either enable or disable the breakup job option for master servers. When the Breakup Jobs option is enabled, OpsCenter collects a greater level of job detail at a file-system level. In addition to other job attributes, OpsCenter collects job attributes like size, file count, and directory name from the master server. For example, when the Breakup Jobs option is enabled, you can see how much data was backed up per file system. You can enable or disable the Breakup Jobs functionality for master server versions earlier than 7.1. The Breakup Jobs option can be enabled or disabled while adding a master server from Settings > Configuration > NetBackup. To enable the Breakup Jobs functionality for master server versions earlier than 7.1, select the Enable Breakup Job data collection option from the Advanced Data Collection Properties section. More information on how to enable or disable the Breakup Jobs functionality for master server versions earlier than 7.1 is available. See Settings > Configuration > NetBackup > Add Master Server options on page 381. The Breakup Jobs functionality is disabled by default for 7.1 master servers. To enable the Breakup Jobs functionality for 7.1 master servers, you must configure the scl.conf file. More information on how you can enable the Breakup Jobs functionality for 7.1 master servers is available. See Configuring the Breakup Jobs option for master servers on page 368. Note: Enabling the Breakup Jobs option increases the load on the master server, the load on the Agent (applicable for master servers earlier than 7.1), and the time it takes to gather and load data in OpsCenter.

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. The job selection is based on the maximum number of files that a job backs up. By default, breakup job information is not collected for jobs whose file count is greater than 1000000. This applies to all master server versions. See Configuring the Breakup Jobs option for master servers on page 368. 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. The Breakup Jobs functionality supports the NetBackup master server versions starting from 6.5. This includes NetBackup 6.5, 6.5.*, 7.0, 7.0.1, and 7.1 master servers. Note that the Breakup Jobs functionality is not supported for NetBackup 6.0 MPx master servers (like 6.0 MP7, 6.0 MP5 etc.). The Breakup Jobs data collection only happens for the jobs that are collected after you upgrade to Symantec OpsCenter Analytics 7.1. The breakup jobs data is not collected for the jobs that already exist in the OpsCenter database. The Breakup Jobs data collection happens through image ID's. Symantec recommends that you enable image data collection for the master server if you want to collect the breakup jobs data. For 7.1 master servers, the image data collection happens automatically by NBSL. For NetBackup master servers before 7.1, you can enable image data collection while adding a master server. See Adding a master server in the OpsCenter console on page 385. The Breakup Jobs option is only valid for the backup jobs and Archive jobs whose Job State is Done. For NetBackup 7.1 master servers, the breakup jobs data is collected directly from the master server by NBSL. For NetBackup master servers earlier than 7.1, the OpsCenter Agent collects the breakup jobs data from the NetBackup master server. Hence if you have a master server version earlier than 7.1 (like 7.0, 7.0.1 etc.) and want to collect breakup jobs data for the master server, you must install the OpsCenter Agent. The OpsCenter Agent uses the bplist command to collect data from the NetBackup master server. More information about deploying the OpsCenter Agent is available. See About OpsCenter Agent deployment on page 95. Data for the breakup jobs is collected from NetBackup after every 15 minutes.

368

Understanding data collection About configuring data collection for NetBackup

The Breakup Jobs functionality applies to Symantec OpsCenter Analytics only. The Breakup Jobs functionality cannot be used with Symantec OpsCenter (free version). If you upgrade from VBR to Symantec OpsCenter Analytics 7.1, the breakup job information from VBR is migrated to the OpsCenter database.

See Viewing the data collection status for breakup jobs on page 370. See About viewing breakup jobs data in custom reports on page 370. See About breakup jobs considerations on page 371.

Configuring the Breakup Jobs option for master servers

You can configure the Breakup Jobs option for master servers from the scl.conf file. You can configure the scl.conf file to enable the Breakup Jobs option for 7.1 master servers (disabled by default). Note that enabling or disabling the Breakup Jobs option using scl.conf applies to 7.1 master servers only. 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. You can also configure the jobs for which you want to collect breakup job information. The job selection is based on the maximum number of files that a job backs up. By default, breakup job information is not collected for jobs whose file count is greater than 1000000. This applies to all master server versions. To enable the Breakup Jobs option for 7.1 master servers

Log on to the OpsCenter Server host. Stop all OpsCenter Server services on Windows and UNIX:
Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop UNIX /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

Open scl.conf file from the following directory on Windows and UNIX:
Windows INSTALL_PATH\OpsCenter\Server\config\scl.conf UNIX /opt/SYMCOpsCenterServer/config

Understanding data collection About configuring data collection for NetBackup

369

The Breakup Jobs option is disabled by default. To enable the Breakup Jobs option for 7.1 master servers, add the following text to scl.conf file:
nbu.scl.collector.enableBreakupJobDataCollection=true

Note: To disable the Breakup Jobs option for 7.1 master servers, add the following text to scl.conf file:
#nbu.scl.collector.enableBreakupJobDataCollection=false

4 5

Save scl.conf file. Restart all OpsCenter Server services on Windows and UNIX:
Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start UNIX /opt/SYMCOpsCenterServer/bin/opsadmin.sh start

To specify the maximum file size of jobs for Breakup Job data collection

Go to theOpsCenter Server host. Stop all OpsCenter Server services on Windows and UNIX:
Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop UNIX /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

Open scl.conf file from the following directory on Windows and UNIX:
Windows INSTALL_PATH\OpsCenter\Server\config\scl.conf UNIX /opt/SYMCOpsCenterServer/config

370

Understanding data collection About configuring data collection for NetBackup

By default, breakup job information is not collected for jobs that back up more than 1000000 files. However, 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 server versions. For example, if you do not want to collect breakup job information for jobs that back up more than 20,000 files, add the following text to the scl.conf file: nbu.scl.collector.breakupJobMaxFileCountPerJob=20000 Once you complete this procedure, breakup job information is not collected for jobs whose file count is greater than 20000. This applies to all master servers.

4 5

Save scl.conf file. Restart all OpsCenter Server services on Windows and UNIX:
Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start UNIX /opt/SYMCOpsCenterServer/bin/opsadmin.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. 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. Click the master server from the Network Name column and then click the Data Collection Status tab. To view the breakup jobs data collection status, check the status for the SubJobs data type.

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. You can see the breakup jobs data by creating custom reports in Symantec OpsCenter Analytics. To view breakup jobs data in Symantec OpsCenter Analytics, 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.

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. This report helps you to know how much data was backed up per job directory. Figure 5-1 Sample custom report that shows breakup jobs data

In this example, you may notice some job directories named Other in addition to the actual job directories from NetBackup. 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. To keep the total backup size consistent, a new job directory named Other is shown to make up the difference. Hence you see some additional file system objects named Other in OpsCenter other than the actual list that comes from NetBackup.

About breakup jobs considerations

Review the following considerations with respect to the Breakup Jobs functionality:

Unlike VBR, OpsCenter does not provide the option to purge breakup jobs. In OpsCenter, the breakup jobs are tightly coupled with jobs and are purged along with the jobs. For a specific job ID in an OpsCenter custom report, breakup job data (like Backup Sub Job File Count, Backup Sub Job Size) is available only for 50 job directories. When a NetBackup policy or job has more than 50 backup selections, breakup jobs data for only 50 backup selections is available with NetBackup. The NetBackup GUI truncates data for the subsequent backup selections (greater than 50).

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. This information is displayed as data is collected by using CLI's and not NBSL.

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.

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

Viewing master server details and data collection status

Use the following procedure to view the details for a master server. The details for the master server are shown at the bottom of the Settings > Configuration > NetBackup view under the following tabs:
General This tab displays the contents of many of the columns that are displayed in the table.

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. The Data Collection Status tab is shown by default when you select Settings > Configuration > NetBackup. It also lists details like the time when the data load was last successful, when data collection last happened, and the exception message if the data collection failed for any of the data types. See 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, select Settings > Configurations > NetBackup. Click the name of the master server (link) from the Network Name column. The details for the master server are shown at the bottom of this view.

Data collection status of a master server

This section describes the NetBackup data types that OpsCenter collects and the different states for managed servers. Figure 5-2 shows a sample data collection status view for a master server. Figure 5-2 Sample Data Collection Status view

Table 5-10 gives a description of the contents in the Data Collection Status tab. Table 5-10 Column
Data Type

Data Collection Status view Description

The type of data that is collected from NetBackup. See NetBackup data types and collection status on page 374.

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. This column lists the date and time when data collection was attempted. This column provides the status of each data load activity that OpsCenter requests. This column lists the last exception message if data collection failed for a data type.

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, policy, media server, service, storage unit etc.) by using NBSL. For most operations and changes in NetBackup, NBSL sends notifications to OpsCenter. For changes such as job, policy, services, and devices, the notification also contains the changed data. This data is stored in the OpsCenter database. The following are the collection statuses for the different data types and their description:

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. For example, NetBackup 6.0 does not support disk, FT data types. This status also comes when your master server version is lower than 7.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. See Adding a master server in the OpsCenter console on page 385. See Editing a master server in OpsCenter on page 386. See Master server states in OpsCenter on page 376. Not Started The data collection for the specific data type has not started. This may happen when you initially add a master server or when you start the OpsCenter server. The data collection for the specific data type is queued. The data collection for the specific data type is in progress. The data collection for the specific data type is complete. The data collection for the specific data type has failed. When the data collection fails, you can see the exception message from the Last Exception Message column.

Queued Running Completed Failed

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

376

Understanding data collection About configuring data collection for NetBackup

See Data collection status of a master server on page 373.

Master server states in OpsCenter

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

Master server state

Connected

Partially Connected

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

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. OpsCenter can monitor the master servers which have NetBackup Access Control (NBAC) configured and also those servers that do not have NBAC configured. Note: Symantec recommends that any NetBackup master server be monitored by only one OpsCenter server. Use the following steps to add a master server. Note that you must first configure the master server to allow server access and data collection by OpsCenter. After configuring the master server, you must add this server to the OpsCenter console so that it can be monitored. To add a master server

Configure your managed master server to allow server access and data collection by OpsCenter. See Configuring a master server for server access and data collection by OpsCenter on page 379.

After configuring the master server, you must add the master server to the OpsCenter console so that it can be monitored. See Adding a master server in the OpsCenter console on page 385.

Note: You can use an alternate procedure to add a NetBackup 7.0 or later master server to OpsCenter. This procedure can be used for both NBAC and non-NBAC servers. See Adding a NetBackup 7.0 or later master server on page 377.

Adding a NetBackup 7.0 or later master server

Use the following procedure to add a NetBackup 7.0, 7.0.1, or 7.1 master server to the OpsCenter console. This procedure can be used for both NBAC and non-NBAC servers. In case of a clustered NetBackup setup, use this procedure for each node of the cluster.

378

Understanding data collection About configuring data collection for NetBackup

To add a NetBackup 7.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. Browse to the following location:
Windows UNIX %Program Files%/NetBackup/bin/admincmd /usr/openv/netbackup/bin/admincmd

Run the following command on the master server:

nbregopsc -add <Name of the OpsCenter Server>

As a part of usability enhancements, a command that is called nbregopsc has been added to NetBackup 7.0 and later versions. In addition, a new entry that is called OPS_CENTER_SERVER_NAME has been added to the bp.conf file. The nbregopsc command registers OpsCenter with the current master server and adds this master server to OpsCenter. This command also establishes a trust relationship from the authentication broker of NetBackup master server to the authentication broker of OpsCenter server.

Understanding data collection About configuring data collection for NetBackup

379

Ignore this step for master servers for which NBAC is not configured. However if the master server is NBAC-enabled, a trust relationship must be established from the authentication broker of the OpsCenter server to the authentication broker (AB) of the NetBackup master server. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server. To establish the trust relationship, log on as Administrator or root on the OpsCenter server host and navigate to the following location:
Windows %Program Files%\Veritas\Security\Authentication\bin /opt/VRTSat/bin

UNIX

On the OpsCenter server host, run the following command depending on your specific master server version:
7.0 and 7.0.1 master server 7.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.

Restart all the NetBackup services (processes). Once you perform this procedure, the master server is automatically added to the OpsCenter console. Note: In case running the nbregopsc command fails, you must manually add the master server to the OpsCenter console. See Adding a master server in the OpsCenter console on page 385.

Configuring a master server for server access and data collection by OpsCenter
Use the following procedures to configure a master server for data collection by OpsCenter on Windows and UNIX. This procedure applies to both NBAC and non-NBAC master servers.

380

Understanding data collection About configuring data collection for NetBackup

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

8 9

Click Close. In the Master Server Properties dialog box, click OK.

Understanding data collection About configuring data collection for NetBackup

381

10 Ignore this step for master servers on which NBAC is not configured.
However if the master server is NBAC-enabled, a bi-directional trust relationship must be established between the authentication broker of the OpsCenter server and the authentication broker(AB) of each managed NetBackup server. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server (NBAC enabled). To set up these trust relationships, use the vssat command in Symantec Product Authentication Service. Run this command from %Program Files%\Veritas\Security\Authentication\bin directory in Windows or /opt/VRTSat/bin in UNIX. On the NetBackup master server host, run the following command:
vssat setuptrust --broker <OpsCenterABhost:2821> --securitylevel high

where <OpsCenterABhost> is same as the host where OpsCenter server is installed. However if OpsCenter is installed in a clustered mode, then <OpscenterAB> is the host name that is provided as the remote authentication broker host during the OpsCenter installation. Similarly, log on as Administrator or root on the OpsCenter server host and run the following command depending on your specific master server version:
7.0 and 7.0.1 master server 7.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.

11 Restart all the NetBackup services. 12 Add this master server to the OpsCenter console so that it can be monitored.
See Adding a master server in the OpsCenter console on page 385.

Settings > Configuration > NetBackup > Add Master Server options
Enter the following detailsforthemasterserverunder GeneralProperties and AdvancedProperties sections:

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. This field is required. In case the master server is clustered, enter the virtual name of the master server.

Display Name

Enter an alternate name for the server. The display name is used for the master server on all views of the OpsCenter console. Note that this field is required.

NetBackup PBX port

The NetBackup PBX port allows all socket communication to take place while connecting through a single port. The default NetBackup PBX port is 1556. Note that this field is required.

OpsCenter's Preferred network address

The OpsCenter server may have multiple network interface cards (NIC). You can select a preferred network address from the drop-down list. OpsCenter uses the address that you select to connect to the master server. After entering the above details, click Locate to locate the master server. The OpsCenter server tries to connect to the master server.

Locate option

The Advanced Data Collection Properties section is applicable if your NetBackup master server version is lower than 7.1. For NetBackup 7.1, all data is collected automatically by NBSL and OpsCenter Agents do not need to be installed on the 7.1 master server. You can configure an Agent to collect the following data from master server versions below 7.1: NetBackup version
6.0.x

Data Collection
Install an Agent if you want to collect data for image or error logs. Install an Agent if you want to collect data for image, error log, scheduled jobs, or breakup jobs. Install an Agent if you want to collect data for breakup jobs.

6.5.x

7.0.x

Understanding data collection About configuring data collection for NetBackup

383

Note: The data for image, error log, scheduled jobs, and breakup jobs is used in OpsCenter reports. 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, the appropriate NatBackup version is automatically selected in the NetBackup version drop-down list.. In case the Locate operation fails and OpsCenter fails to connect to the master server, select the appropriate master server version manually from the drop-down list. You can select from the following versions:

6.0.x 6.5.x 7.0.x 7.1.x

Agent

Select an agent from the drop-down list. In case, no agent is configured, click Configure Agent. You can create an OpsCenter Agent from Settings > Configuration > Agent > Create Agent. See Configuring an OpsCenter Agent on page 355.

Install Directory

The directory path on the OpsCenter Agent host where the NetBackup application is installed. In case of remote data collection, this is the path on the OpsCenter Agent host where RAC (Remote Admin Console) is installed. Example of install directory path on a Windows machine: C:\Program Files\VERITAS\NetBackup Example of install directory path on a Solaris machine: /usr/openv/netbackup

Volume Manager Directory The directory path on the OpsCenter Agent host where the Volume Manager is installed. Example of Volume Manager directory on a Windows machine: C:\Program Files\VERITAS\Volmgr Example of Volume Manager directory on a Solaris machine: /usr/openv/volmgr

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 option appears only when you add 6.0.x or 6.5.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. This option appears only when you add 6.0.x or 6.5.x master servers.

Enable Scheduled Job Data Collection

Click the checkbox if you want to enable scheduled job data collection from the master server. This option appears only when you add 6.5.x master servers. For 6.0 MP7 master servers, you cannot collect scheduled jobs data. Note that you must enter the value in Username and Password fields so that scheduled job data can be collected.

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 feature is most effective if you have multiple paths in your backup selection lists in NetBackup. This option appears only when you add 6.5.x, or 7.0.x master servers. For 6.0 MP7 master servers, you cannot collect breakup jobs data. The breakup jobs data is automatically collected for 7.1 master servers.

Note: Enabling this option increases the load on the

OpsCenter Agent, the master server, and the time it takes to collect and load data in OpsCenter.

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. A user name is required if you enable scheduled job data collection. Ignore this field in the following scenarios:

If you have set the Scheduled Jobs option to Disable If you want to collect the scheduled jobs data from a local NetBackup host.

If you want to collect the scheduled jobs data remotely, using the nbpemreq CLI, set the Future Scheduled Jobs option to Enable, and specify valid NetBackup admin credentials.

Note: The Username field is disabled if Enable Scheduled

Job Data checkbox is unchecked.

Note: Username and Password is not needed if the agent is

installed on NBU master server. Password Enter the password of the NetBackup user account. This is required if you enable scheduled job data collection.

Note: The Password field is disabled if Enable Scheduled

Job Data checkbox is unchecked. Save / Cancel options Click Save to add the master server. Click Cancel to exit and go back to the Settings > Configuration > NetBackup page.

Adding a master server in the OpsCenter console

You must add a master server to the OpsCenter console so that it can be monitored. Use the following procedure to add a master server. To add a master server

1 2

In the OpsCenter console, select Settings > Configurations > NetBackup . Click Add.

386

Understanding data collection About configuring data collection for NetBackup

Enter the detailsforthemasterserverunder GeneralProperties and AdvancedProperties sections . See Settings > Configuration > NetBackup > Add Master Server options on page 381. The Advanced Data Collection Properties section is applicable if your NetBackup master server version is lower than 7.1. For master server versions below 7.1, you must install an Agent to collect the data for image, error log, scheduled jobs, or breakup jobs as per the master server version. For NetBackup 7.1, this data is collected automatically by NBSL and OpsCenter Agents do not need to be installed on the 7.1 master server. The data for image, error log, scheduled jobs, and breakup jobs is used in OpsCenter reports. Enter the details under Advanced Data Collection Properties section, if applicable. See Settings > Configuration > NetBackup > Add Master Server options on page 381.

Click Locate to check if OpsCenter can connect to the master server. An error appears if OpsCenter cannot connect to the NetBackup master server on the network. Click Save to add the master server. Alternately, you can click Cancel to exit.

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, select Settings > Configurations > NetBackup. Use the checkbox to select a master server from the Network Name column. Click Edit.

Understanding data collection About configuring data collection for NetBackup

387

Edit the information that is displayed on the Edit Master Server page. You can change the data that is shown for General Properties, Advanced Properties, and Advanced Data Collection Properties sections. A description of the fields present in these sections is available. See Adding a master server in the OpsCenter console on page 385. Note that you cannot edit the Network Name for the master server. The Network Name field falls under the General Properties section.

Click Save.

Deleting a master server in OpsCenter

You can delete one or more master servers using the following procedure. Note that deleting a master server deletes all the data that is associated with the master server. Note: Deleting a master server may take some time. To delete a master server

1 2 3 4

In the OpsCenter console, select Settings > Configurations > NetBackup . Use the checkbox to select one or more master servers from the Network Name column. Click Delete. The following warning message appears:
Deletion of the selected master server(s) will delete all related data. Do you want to proceed?

Click OK.

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: If you disable data collection it may appear to be a loss of data in OpsCenter. For example, a drive may have the same status until you enable OpsCenter data collection again.

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 Settings > Configurations > NetBackup. Use the checkbox to select one or more master servers from the Network Name column. Click Disable Data Collection.

To enable data collection for a master server

1 2 3

In the OpsCenter console, select Settings > Configurations > NetBackup . Use the checkbox to select one or more master servers from the Network Name column. Click Enable Data Collection.

Configuring Backup Exec data collector

This section describes data collection from Backup Exec. Caution: The Backup Exec data collector requires the following component to be installed on the OpsCenter Agent host, to collect data properly. Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) that is vcredist_x86.exe VC Redistributable Package is available at: http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en Once you install this component on the Agent host, configure the Backup Exec data collector as described in the following section. To configure Backup Exec data collector

1 2 3 4 5 6

Click Settings > Configuration > Agent. On the Agent list, select a check box in front of the Agent, for which you want to configure a Data Collector. Click Create Data Collector. On the CreateDataCollector:ProductSelection page, select Symantec Backup Exec from the Select Product drop-down list. In the Target Host Name text box, enter the Backup Exec Server host name, from which you want to collect data. Click Next.

Understanding data collection Collecting data from PureDisk

389

On the Create Data Collector: Details page, specify the following Backup Exec data collector configuration settings:
User name Enter the name of the user account that is required to connect to the Backup Exec Database . Enter the password of this user account. Select the version of the Symantec Backup Exec server - 10.x, 11.x, or 12.x - from which you want to collect data.

Password Version

Select blackout period details, data types to be collected, and collection interval. For more details on collection interval, and other data collector settings, refer to the following section: See Configuring an OpsCenter Data Collector on page 358.

Click Save.

Collecting data from PureDisk

OpsCenter supports collection of data from Symantec NetBackup PureDisk. The collected data is stored in the OpsCenter database, based on which you can generate reports. OpsCenter can collect Policy & Schedule and Job data types from PureDisk Storage Pool Authority (PureDisk SPA). For more details on PureDisk, refer to the Symantec NetBackup PureDisk documentation. PureDisk SPA and its components that run on the PureDisk operating system (PDOS). The Single Instance Storage (SIS) or deduplication technology of NetBackup PureDisk is unique in storage and backup industry. PureDisk identifies files and the data segments that contain identical data and treats them as a single instance of a file, which it backs up only once. This lets you save storage space. Attributes of identical files, such as name and date of modification can vary. While backing up a file, PureDisk determines whether multiple instances of the file are present on hosts across the network, including remote hosts. By using the deduplication technology, PureDisk stores only one instance of the file. Table 5-15 describes the steps that you need to carry out to collect data from PureDisk.

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 number Step

Step 1 Install OpsCenter server.

Note: When you install OpsCenter

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

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. SPA host and OpsCenter AB host This is a pre-requisite for PureDisk data collection on page 390. from OpsCenter. Using the OpsCenter console, configure PureDisk See Configuring data collector for the Integrated Agent. PureDisk data collector on page 391.

Step 3

See Setting up a trust between the PureDisk SPA host and OpsCenter AB host on page 390. See Configuring PureDisk data collector on page 391.

Setting up a trust between the PureDisk SPA host and OpsCenter AB host
You need to set up a bi-directional trust between the PureDisk SPA host and OpsCenter AB (authentication broker ) host. This is a pre-requisite for PureDisk data collection from OpsCenter.

Understanding data collection Collecting data from PureDisk

391

Note: OpsCenter AB host is the host where the OpsCenter server is installed. However, if OpsCenter is installed in a clustered mode, then the OpsCenter AB host is the host name that was provided as the remote authentication broker host during the OpsCenter installation. The OpsCenter AB hostname is stored in the vxss.hostname parameter in the following file: On Windows: C:\Program
Files\Symantec\OpsCenter\server\config\security.conf

On UNIX: /opt/SYMCOpsCenterServer/config/security.conf This section provides the manual steps that you need to carry out on the PureDisk SPA host, to setup trust between the PureDisk SPA host and the OpsCenter authentication broker host. To set up a trust between PureDisk SPA host and OpsCenter AB host

On the PureDisk SPA host, logon as root and run the following command:
su www-data

As a www-data user, run the following command:

/opt/VRTSat/bin/vssat setuptrust --broker OpsCenterABhost:2821 --securitylevel low

After successfully setting up a trust between the PureDisk SPA host and OpsCenter AB host, the following message is displayed:
setuptrust ------------------------------------------Setup Trust With Broker: OpsCenterABhost

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.

392

Understanding data collection About collecting data from Enterprise Vault

To configure NetBackup PureDisk data collector

1 2

Click Settings > Configuration > Agent. On the Agent list, select a check box in front of the Integrated Agent. When you install OpsCenter server,OpsCenter Integrated Agent is also installed and configured, which you can use to collect only PureDisk data. To collect PureDisk data, you do not need to manually install or configure OpsCenter Agent. You can collect PureDisk data only through the OpsCenter Integrated Agent.

3 4 5 6 7

Click Create Data Collector. On the Create Data Collector: Product Selection page, select Symantec NetBackup PureDisk from the Select Product drop-down list. In the Target Host Name text box, enter the PureDisk SPA Server host name, from which you want to collect data. Click Next. On the Create Data Collector: Details page, specify the following PureDisk configuration settings:
Product Version Select any of the following Symantec NetBackup PureDisk versions from the drop-down list: 6.2, 6.2.1, 6.2.2, 6.5, 6.5.0.1, 6.5.1, 6.6, 6.6.0.1, 6.6.0.2, 6.6.0.3

For more details on collection interval, and other data collector settings, refer to the following section: See Configuring an OpsCenter Data Collector on page 358.

Click Save. Setting up a trust between the OpsCenter authentication broker host and PureDisk SPA host is accomplished automatically after PureDisk data collector is configured. If it is not successful, you need to do it manually. Refer to Setting up a trust between the OpsCenter AB host and PureDisk SPA host in the OpsCenter Administrator's Guide.

About collecting data from Enterprise Vault

The following topics provide information about Enterprise Vault Data Collector configuration. See About Enterprise Vault on page 393.

Understanding data collection About collecting data from Enterprise Vault

393

See About data collected from Enterprise Vault on page 393. See Versions supported by OpsCenter on page 396. See Planning the Enterprise Vault data collector deployment on page 396. See OpsCenter Agent deployment modes on page 398. See Accessing MS SQL Server host on page 398. See About creating a user for integrated logon on page 399. See Configuring the OpsCenter Agent properties for integrated logon on page 401. See Installing MS SQL Server JDBC driver on page 402. See Configuring Enterprise Vault data collector on page 403.

About Enterprise Vault

Symantec Enterprise Vault software application provides a flexible framework for archiving emails, file systems, and collaborative environments. It is supported only on Windows platform. Enterprise Vault has the following features:

Policy-controlled archiving Seamless retrieval of information Powerful search capability Compliance retention Data compression and single instancing

For more details, refer to Enterprise Vault documentation.

About data collected from Enterprise Vault

OpsCenter categorizes the data that is collected from Enterprise Vault database into various data types. Table 5-16 lists the data types in OpsCenter that represent type of data that is collected from Enterprise Vault. For example, OpsCenter collects Policy and Retention Category data from Enterprise Vault database and stores it as Archive Policy data type.

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, Vault Store, and Vault Store Partition Mailbox, Public Folder, and Provisioning Group SaveSet

Data type in OpsCenter

Archive Policy Vault Store

Target Archive

You can select these data types while configuring the Enterprise Vault data collector. The data collector collects the information from Enterprise Vault that is associated with the selected data types, , as per the specified schedule. See Configuring Enterprise Vault data collector on page 403. Figure 5-3 shows the hierarchy of archive data in Enterprise Vault.

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, Provisioning Groups), storage media (vault store groups, vault stores, vault partitions), and Enterprise Vault Servers. It is at the highest level in the Enterprise Vault data hierarchy. Using OpsCenter archive reports you can

396

Understanding data collection About collecting data from Enterprise Vault

determine the details about both archiving activities and archival storage, depending on which path you follow to drill down the site information. See About OpsCenter reports on page 579. OpsCenter reports present archive data in the following two ways:
Archiving activities A few archive reports show details about archiving activities. For example: Details of mailboxes to be archived, original size of data that has been archived, the number of mailboxes that exceed their warning limits per Exchange Server or Provisioning Group, and so on. These are all archiving activities, which you can view reports for. These archiving activity reports are available in the Exchange report folder of Archive reports. OpsCenter archive reports show only Exchange Server data.

Note: Mailboxes are referred to as targets and an individual email

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

Versions supported by OpsCenter

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

Planning the Enterprise Vault data collector deployment

Enterprise Vault stores archive metadata in the directory and the Vault Store database. To collect the archive metadata from Microsoft SQL Server, you need to configure OpsCenter Agent and data collector using the OpsCenter console. OpsCenter supports local as well as remote archive-data collection. In the remote data collection method, OpsCenter Agent and MS SQL Server are installed on different hosts. 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.

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, to collect archive data remotely: deployment modes on page 398. 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. rights on the MS SQL Server, where the archive data resides. This can be an existing user, or you can create a new user in MS SQL Server and give required access rights.

Step 3

Depending on the deployment mode of the OpsCenter Agent, add a user in the appropriate domain or workgroup, which you want to use for integrated logon between Agent host and MS SQL Server host.

See About creating a user in single-domain deployment mode on page 399. See About creating a user in multi-domain deployment mode on page 400. See About creating a user in standalone deployment mode on page 400.

Step 4

Install MS SQL Server JDBC driver on the OpsCenter Agent host.

See Installing MS SQL Server JDBC driver on page 402. See Configuring the OpsCenter Agent properties for integrated logon on page 401.

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, where the Enterprise Vault data resides, depending on the OpsCenter Agent deployment mode.

You need to configure the Enterprise Vault data collector using the OpsCenter console and schedule data collection. See Configuring Enterprise Vault data collector on page 403.

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, depending on your setup. This section mainly talks about the remote agent deployment modes. However, Enterprise Vault also supports local Agent deployment. You can deploy the OpsCenter Agent on MS SQL Server host or OpsCenter Server host. Table 5-18 Agent deployment modes Description
In a single-domain deployment mode, the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) share the same Windows domain. In addition to single-domain mode, you can deploy the OpsCenter Agent in multi-domain mode. In this deployment mode, the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. The OpsCenter Agent host is in a domain different than the SQL Server domain. In this deployment mode, the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. The OpsCenter Agent host is installed on a standalone host.

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. To access MS SQL Server host

1 2

Create a Windows domain user on the MS SQL Server host. For example, create a user with credentials of username: localadmin and password: pass. Open the MS SQL Server admin console, using SQL Server Management Studio Express or any other MS SQL Server client. Add this Windows domain user (local admin) to the MS SQL Server.

Understanding data collection About collecting data from Enterprise Vault

399

Add this user (local admin) to the Enterprise Vault databases, on which you want the access rights. Note: To report on Enterprise Vault / archive data, OpsCenter Agent needs access to the Enterprise Vault directory and storage databases. You need to add the user to these databases and give the required access rights on these databases.

4 5 6

In the MS SQL Server admin console, in the Object Explorer, expand the Security folder. Expand the logons folder. Right-click the user name - for example username: OpsDomain\localadmin with the password: pass - with which you want to perform integrated logon on the Agent host and MS SQL Server host. Click Properties. On the logon Properties screen, in the Select a page pane, select Server Roles. In the right-hand Server roles pane, select the public check box. The user local admin in the OpsDomain (OpsDomain\localadmin) now has the rights to access MS SQL Server.

7 8 9

10 Additionally, make sure that the user has datareader rights to access the
desired database.

About creating a user for integrated logon

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

About creating a user in single-domain deployment mode

Make sure that the user whose credentials (for example, User name: localadmin and Password: pass) you use for the integrated logon has required access rights on the MS SQL Server, where the archive data resides.

400

Understanding data collection About collecting data from Enterprise Vault

The user localadmin can be an existing user, or you can create a new user with these credentials in MS SQL Server and give required access rights. See Accessing MS SQL Server host on page 398. If you have deployed the OpsCenter Agent in the single-domain mode, create a user, (User name: localadmin and Password: pass) in the Agent host domain that is the Windows domain. See OpsCenter Agent deployment modes on page 398. Use credentials of this user (User name: localadmin and Password: pass) when you configure the Agent properties for integrated logon. See Configuring the OpsCenter Agent properties for integrated logon on page 401.

About creating a user in multi-domain deployment mode

Make sure that the user whose credentials (for example, User name: localadmin and Password: pass) you use for the integrated logon has required access rights on the MS SQL Server, where the archive data resides. The user localadmin can be an existing user, or you can create a new user with these credentials in MS SQL Server and give required access rights. See Accessing MS SQL Server host on page 398. If you have deployed the OpsCenter Agent in the multi-domain mode, create a user (User name: localadmin and Password: pass) in the Agent host domain. See OpsCenter Agent deployment modes on page 398. Use credentials of this user (User name: localadmin and Password: pass) when you configure the Agent properties for integrated logon. See Configuring the OpsCenter Agent properties for integrated logon on page 401. If the Agent host is on a different domain as compared to the EV host, then the user must be created as a local Administrator. This is because the Agent domain is not visible to the EV host.

About creating a user in standalone deployment mode

Make sure that the user whose credentials (for example, User name: localadmin and Password: pass) you use for the integrated logon has required access rights on the MS SQL Server, where the archive data resides. The user localadmin can be an existing user, or you can create a new user with these credentials in MS SQL Server and give required access rights. See Accessing MS SQL Server host on page 398.

Understanding data collection About collecting data from Enterprise Vault

401

If you have deployed the OpsCenter Agent in the standalone mode, create a user for example (User name: localadmin and Password: pass) in the Administrator workgroup. See OpsCenter Agent deployment modes on page 398. Use credentials of this user (User name: localadmin and Password: pass) when you configure the Agent properties for integrated logon. See Configuring the OpsCenter Agent properties for integrated logon on page 401.

Configuring the OpsCenter Agent properties for integrated logon

The Enterprise Vault data collector that is configured in OpsCenter collects the Enterprise Vault archive data residing on the MS SQL Server. However, the data collection is not possible if the OpsCenter Agent is not configured to run in the context of the user or the group that has access to the SQL Server. Note: Make sure that this user has required rights to access MS SQL Server See Accessing MS SQL Server host on page 398. To configure OpsCenter Agent properties

1 2 3

On the OpsCenter Agent host (Windows system), click Start > Run. In the Run dialog box, in the Open text box, enter services.msc. Click Enter. The Windows Services screen is displayed.

4 5 6 7

On the Services screen, on the services list, right-click the Symantec OpsCenter Agent service. On the right-click menu, click Properties. On the Symantec OpsCenter Agent Properties screen, on the Log On tab, select the This account option. Enter the credentials of the user - for example localadmin with the password: pass - who has the rights to access the MS SQL Server, where the Enterprise Vault archive data resides. Alternatively, click Browse. This opens the Select User dialog box.

Enter a user name in the text box. This user should have access rights on MS SQL Server. Click Check Names to check whether the user name that is specified is present in the Windows domain or not.

402

Understanding data collection About collecting data from Enterprise Vault

Click OK.

10 Click OK on the LogOn tab.

Installing MS SQL Server JDBC driver

To collect the Enterprise Vault data residing on Microsoft SQL Server (or MS SQL Server or SQL Server), you require the SQL Server JDBC driver that is installed on the OpsCenter Agent host. The Agent requires the JDBC driver to communicate with the MS SQL Server. Microsoft provides a Java Database Connectivity (JDBC) driver for use with SQL Server. The SQL Server JDBC Driver 2.0 is available to all SQL Server users at no additional charge, and provides access to SQL Server 2000, SQL Server 2005, and SQL Server 2008 from any Java application, application server, or Java-enabled applet. This is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in Java Platform, Enterprise Edition 5. To install MS SQL Server JDBC driver

Click the following link: Download Microsoft SQL Server JDBC Driver 2.0

2 3

On the Microsoft SQL Server JDBC Driver 2.0 page, click Download. The File Download dialog box is displayed. Click Open to access the end-user license agreement.

On the MICROSOFT SOFTWARE LICENSE TERMS page, 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.0.1803.100_enu.exe file to a desired location. Unzip the sqljdbc_2.0.1803.100_enu.exe file.

Understanding data collection About collecting data from Enterprise Vault

403

Copy sqljdbc_2.0\enu\auth\x86\sqljdbc_auth.dll and sqljdbc_2.0\enu\sqljdbc4.jar files to the following location on the Agent host.
Install Dir\Symantec\OpsCenter\Agent\lib

where Install Dir is the location where you have installed OpsCenter. Click the following link for more information and frequently asked questions on the JDBC driver. Microsoft SQL Server JDBC Driver

Restart the Agent service.

Configuring Enterprise Vault data collector

This section provides the procedure to configure the Enterprise Vault data collector in the OpsCenter console. This data collector collects archive data from MS SQL Server where the Enterprise Vault database resides. To collect archive data, the Enterprise Vault data collector needs the Agent to be configured to run in the context of the user or the group that can access MS SQL Server. See Configuring the OpsCenter Agent properties for integrated logon on page 401. To configure Enterprise Vault data collector

1 2 3 4 5 6 7

In the OpsCenter console, click Settings > Configuration > Agent . On the Agent list, select a check box in front of the Agent for which you want to configure the Data Collector. Click Create Data Collector. On the Create Data Collector: Product Selection page, select Symantec Enterprise Vault from the Select Product drop-down list. Enter the name of the host, from where you want to collect the archive data. Click Next. Enter the following Configuration Settings:
Database Instance Name This is the directory database instance name. By default this field is left blank.

Databaseportnumber Enter the port number that is used to connect to the MS SQL Server. The default port number is 1433.

404

Understanding data collection About collecting data from Enterprise Vault

8 9

Specify blackout period details. Select the data types that you want to collect. You can collect the following data types from an Enterprise Vault set up: Target, Vault Store, Archive Policy, and Archive.

10 Select collection interval.

For more details on collection interval, and other data collector settings, refer to the following section: See Configuring an OpsCenter Data Collector on page 358.

11 Click Save.
See Enterprise Vault data collection checklist on page 404.

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 OpsCenter Agent has been configured to run in the context of the user or user group that has access to MS SQL Server database where Enterprise Vault data is stored. See Configuring the OpsCenter Agent properties for integrated logon on page 401. The OpsCenter Agent service is running. The SQL Server services are running. You have entered the appropriate information for Enterprise Vault data collector variables. See Configuring Enterprise Vault data collector on page 403. You have selected the data types and events to be collected from the Enterprise Vault database, that is the MS SQL Server. You have specified the collection interval within which you want to collect the archive data.

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. (This variable can be left blank.) An administrator-level logon that is used to connect to the Tivoli Storage Manager server. (The default is admin.) The password for the account (specified in tsmId) for connecting to the TSM server. (The default password is admin.) (Windows only) The TCP port on the TSM server through which the data collector establishes a connection. The TSM Server Port has no effect on Solaris. The Solaris data collector uses only product host settings. dsmConfig dsmDir dsmadmc Location The path to the dsm.opt file. The path where files to be run dsmadmc reside. The path of TSM administrative client (dsmadmc).

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.opt and dsm.sys (Solaris and AIX). For more information, refer to your TSM documentation. Specify the TSM server host (also called product host) value for the TSM data collector in the following manner:

406

Understanding data collection EMC NetWorker data collector variables

Windows

Use the fully qualified host name. In short, product host is the value that you can use with the dsmadmc -tcpserveraddress option. For example, the following entries are valid for product host: Host.sample.domain.com Host assuming that Host can be fully qualified.

Solaris and AIX

The product host must be the value that is specified in the dsm.sys file, for tag SErvername (note the case). In short, product host is the value that you can use with the dsmadmc -se option. The following is a sample dsm.sys file: ***************************************** SErvername server_a COMMmethod CoMMmethod TCPPort TCPip 1500

TCPServeraddress 255.255.255.255 SERVERNAME MYHOST.Veritas.COM TCPSERVERADDRESS 255.255.255.255 NODENAME myhost.mycompany.com

******************************************

For more details on collection interval, and other data collector settings, refer to the following section: See Configuring an OpsCenter Data Collector on page 358.

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.

Understanding data collection EMC NetWorker data collector variables

407

Location of messages file

The directory path for the log file containing group-complete messages. This path may be absolute or relative to homeDirectory. The default file name is messages. To increase the efficiency of the NetWorker data collector, configure NetWorker to create a log that contains only group complete messages, and point messagesFile to this log

Location of mminfo.exe

The directory path of the mminfo command-line interface (CLI), absolute, or relative to homeDirectory The directory path of the nsradmin CLI, absolute, or relative to homeDirectory The NetWorker resource file to use instead of the default file that is used by nsradmin (Optional) Output of an nsradmin command (Optional) The OpsCenter console displays nsrResFile, nsrFile, and mminfoFile even though these variables are optional and only advanced users must set them.

Location of nsradmin.exe

Location of nsrres file

Location of nsr file

Location of mminfo file

Output of mminfo(Optional)

For more details on collection interval, and other data collector settings, refer to the following section: See Configuring an OpsCenter Data Collector on page 358.

408

Understanding data collection EMC NetWorker data collector variables

Chapter

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. Figure 6-1 shows the details that are displayed on the Views tab in the OpsCenter console.

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. However, you cannot modify its attributes because you do not have the write permissions for that view.

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

Managing OpsCenter views About OpsCenter views

411

After you install and run the OpsCenter Server and the OpsCenter Agent, OpsCenter detects the IT assets, which are then stored in the database. The Java View Builder makes these IT assets available when a view is created. The hierarchy of an object view based on archive data is as follows: Abstract objects (Geography > Region > City) > Domain (Site) > Host (Exchange Server / Enterprise Vault server ) > Target (Mailbox / Journal Mailbox / Public Folder) See About collecting data from Enterprise Vault on page 392. Note: To run the Java View Builder, you need Java Runtime Environment (JRE) installed on the host. In a view hierarchy, between top and bottom levels you can create a number of user-defined levels. An OpsCenter view is a homogeneous one, it cannot have hosts and file systems in the same tree.

Settings > Views options

A description of the Views tab options follows in the table. Table 6-1 Option
View Type

Views tab options Description

Select the type of view from the drop-down list. The options are All Views, Client, Master Server, and Policy. See OpsCenter view types on page 412.

Add/Edit/Delete

Select to add new views, or to edit and delete the available views. Select to edit the view level aliases. Select to view the objects on the node and unassigned objects. Displays the name of the view. Displays the date and time when the view was created. Displays the role of the user who created the view. Displays the alias levels for the selected view.

Edit View Level Alias Manage Nodes and Objects

Name Created On Owner View Level Alias

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, description, date and time of creation, and owners role.

Two tabs appear in the Details pane of the Settings > Views page. 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. Default view level aliases are as follows: Level 1, Level 2, and so on. The Alias View Levels tab does not contain any data, if you have not added any nodes or objects to the selected view. You can modify the view level aliases. See Modifying alias view levels in OpsCenter on page 416.

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.

OpsCenter view types

In OpsCenter, each view is associated with a view type. Depending on the type of the view, objects are made available for assigning to that view. Note: All Veritas Backup Reporter (VBR) views are migrated to OpsCenter as Client views. Media reports run only on Master Server view. After you upgrade from VBR, you need to recreate the Master Server views to run the Media reports with views. You can create views of the following types:

Managing OpsCenter views About OpsCenter views

413

Client

If you create a view of type Client, only backup clients are available to be assigned to the view. If you create a view of type Master Server, only Master Servers are available to be assigned to the view. If you create a view of type Policy, only policies are available to be assigned to the view. If you create a view of type Enterprise Vault server, only EV servers are available to be assigned to the view. If you create a view of type Exchange server, only Exchange servers are available to be assigned to the view. If you create a view of type Vault, only vaults are available to be assigned to the view. If you create a view of type File System, only file systems are available to be assigned to the view.

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. A view can either be public or private. See Creating OpsCenter views on page 415.
Public view Private view All OpsCenter users can access public views. Only view owner and OpsCenter admin can access private views.

About OpsCenter view levels

A newly created view has only one level. You can add multiple nodes to a view at different levels. You can add alias for each of these view levels. See Modifying alias view levels in OpsCenter on page 416. Master server hosts, clients, or policies are always at the lowest levels in a view. Between the top level and the bottom level, you can create multiple intermediate

414

Managing OpsCenter views About managing OpsCenter views

levels to organize view objects into logical groups, creating a hierarchical structure in the view.

About nodes and objects

An OpsCenter view comprises nodes and view objects. A node is a logical entity that you add to create a hierarchical structure of a view. Between the first level (the view name itself) and the last level (actual view object), you can add multiple nodes. Figure 6-2 shows an example of a view comprising multiple nodes and objects. Figure 6-2 View nodes and objects

About managing OpsCenter views

The following topics provide procedures to add, edit, or delete OpsCenter views. See Viewing OpsCenter views and their details on page 415. See Creating OpsCenter views on page 415. See Modifying OpsCenter views on page 415. See Deleting OpsCenter views on page 416. See Modifying alias view levels in OpsCenter on page 416.

Settings > Views > Manage Nodes and Objects options

A description of the Settings > Views > Manage Nodes and Objects options follows in the table.

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 Unassigned Objects tab contains all objects that have not yet been assigned to the selected view or view node. The available objects list varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection.

Objects on Node tab

Unassigned Objects tab

Viewing OpsCenter views and their details

This topic provides the procedure to view OpsCenter views. See About OpsCenter views on page 409. To view OpsCenter views

In the OpsCenter console, click Settings > Views. A list of views that you have already created is displayed. See Modifying OpsCenter views on page 415. See Creating OpsCenter views on page 415.

To check the details of a view, select the view from the views list. The View Level Alias and General details are displayed in the lower section of the page. See Settings > Views options on page 411.

Creating OpsCenter views

This topic provides the procedure to create a view using OpsCenter. To create a OpsCenter view

1 2 3 4

In the OpsCenter console, click Settings > Views. Click Add. On the Add View dialog box, specify the view details. Click OK.

Modifying OpsCenter views

This topic provides the procedure to modify view details.

416

Managing OpsCenter views About managing OpsCenter views

To modify OpsCenter views

1 2 3 4 5

In the OpsCenter console, click Settings > Views. From the list of views, select a view that you want to modify. Click Edit. On the Edit View dialog box, you can modify the view details. Click OK.

Deleting OpsCenter views

This topic provides the procedure to delete views. Note: Once you have deleted a view, it cannot be recovered. If you delete a view, all its nodes are deleted and the objects are moved to the unassigned tree. To delete OpsCenter views

1 2 3

In the OpsCenter console, click Settings > Views. From the list of views, select a view that you want to delete. Click Delete.

Modifying alias view levels in OpsCenter

This topic provides the procedure to modify alias of view levels. See Adding nodes to a view in OpsCenter on page 417. See About managing nodes and objects in OpsCenter on page 417. To modify alias view levels in OpsCenter

1 2 3

In the OpsCenter console, click Settings > Views. From the list of views, select a view for which you want to modify view level alias. Click Edit Alias View Levels.

Managing OpsCenter views About managing nodes and objects in OpsCenter

417

On the Alias View Levels dialog box, text boxes for entering aliases for all available view levels appear. For example, if the selected view has only one level, the Alias View Levels dialog box appears as follows:

Rename the available levels. For example, if the selected view has three levels, you can rename the levels as follows: rename Alias Level 1 as Geography, Alias Level 2 as Country, and Alias Level 3 as Region. Click OK.

About managing nodes and objects in OpsCenter

The following topics provide procedures to create, modify, and delete nodes and objects related to a view. See Adding nodes to a view in OpsCenter on page 417. See Modifying node details in OpsCenter on page 418. See Deleting nodes in OpsCenter on page 418. See Adding objects to a view node in OpsCenter on page 419. See Deleting objects from a view node in OpsCenter on page 419. See View filters in OpsCenter on page 420.

Adding nodes to a view in OpsCenter

This topic provides the procedure to add a node to a view. See About nodes and objects on page 414. To add nodes to a view

1 2 3

In the OpsCenter console, click Settings > Views. From the list of views, select a view to which you want to add nodes and objects. Click Manage Nodes and Objects.

418

Managing OpsCenter views Modifying node details in OpsCenter

4 5 6 7

On the view tree, select the view to which you want to add a node. Click Add. On the Add dialog box, enter the node name. Click OK.

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. To modify node information

1 2 3 4 5 6 7 8

In the OpsCenter console, click Settings > Views. From the list of views, select a view to modify the information of associated nodes. Click Manage Nodes and Objects. On the view tree, expand the view to see the associated nodes. Select the node that you want to modify. Click Edit. On the Edit dialog box, modify the name of the node. Click OK.

Deleting nodes in OpsCenter

This topic provides the procedure to delete the nodes from a view. See Adding nodes to a view in OpsCenter on page 417. To delete a node

1 2 3 4 5 6 7

In the OpsCenter console, click Settings > Views. From the list of views, select a view from which you want to delete nodes. Click Manage Nodes and Objects. On the view tree, expand the view to see the associated nodes. Select the node that you want to delete. Click Delete. On the confirmation dialog box, click OK.

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. To add an object to a view node

1 2 3 4 5

In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to add objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node to which you want to add an object. In the right-hand pane, select the Unassigned Objects tab. The available objects list varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection. The Unassigned Objects tab contains all objects that have not yet been assigned to the selected view or view node. You can filter the unassigned objects with the help of default filters. Or you can create new filters and apply them to view the required objects on the tab. See View filters in OpsCenter on page 420.

6 7

Select the check boxes in front of the view objects that you want to add to the selected view or view node. Click Add to Node. The added view objects are removed from the Unassigned Objects tab and appear on the Objects on Node tab.

Deleting objects from a view node in OpsCenter

This topic provides the procedure to delete the objects from a view or a view node. To delete an object from a view node

1 2 3

In the OpsCenter console, click Settings > Views. From the list of views, select the view from which you want to delete objects. Click Manage Nodes and Objects.

420

Managing OpsCenter views View filters in OpsCenter

On the view tree, select the view name or a view node from which you want to delete an object. The objects that are assigned to this view or the view node are displayed on the Objects on Node tab.

5 6 7

Select the check boxes in front of the view objects that you want to delete. Click Delete from Node. On the confirmation dialog box, click OK.

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. You can also create your own filters and apply them to view the required list of view objects. The default set of filters varies depending on the view type. Table 6-4 lists the default filters available for various view types. Table 6-4 View type
Client

Default filters Default filters

All Clients, Windows Clients, Solaris Clients, Linux Clients, Other Clients All Servers, Connected Servers, Partially Connected Servers, Not Connected Servers, Windows Servers, Solaris Servers, Linux Servers, Other Servers All Policies, Active Policies, Inactive Policies, Windows Policies, Catalog Policies, Standard Policies, Other Policies

Master Server

Policy

See the following topics for information about creating, modifying, and deleting view object filters.

Creating a view object filter in OpsCenter

This topic provides the procedure to create user-defined view object filters. See View filters in OpsCenter on page 420. To create a view object filter

1 2

In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to assign objects.

Managing OpsCenter views View filters in OpsCenter

421

3 4 5

Click Manage Nodes and Objects. On the view tree, select the view name or the view node to which you want to assign view objects. In the right pane, select the Unassigned Objects tab. The list of objects that is displayed varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection.

6 7

Click the Create Filter icon. In the Add Filter dialog box, specify the filter details. The following figure shows an example of creating a filter.

Click OK. This user-defined filter is now added in the Filter drop-down list on the Unassigned Objects tab, which you can modify or delete. See Modifying view object filters in OpsCenter on page 421. See Deleting view object filters in OpsCenter on page 422.

Modifying view object filters in OpsCenter

You can modify definition of user-defined view object filters. You cannot modify the default filters. See Creating a view object filter in OpsCenter on page 420. To modify view object filters

1 2 3 4

In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to assign objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node to which you want to assign view objects.

422

Managing OpsCenter views View filters in OpsCenter

In the right pane, select the Unassigned Objects tab. The list of objects that is displayed varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection.

6 7

From the Filter drop-down list, select the user-defined filter that you want to modify. Select the Edit Filter icon. If you have selected a default filter, the Edit Filter icon is disabled.

8 9

On the dialog box, modify name or definition of the filter. Click OK.

Deleting view object filters in OpsCenter

You can delete user-defined view object filters. You cannot delete the default filters. See Creating a view object filter in OpsCenter on page 420. To delete view object filters

1 2 3 4 5 6

In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to assign objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node to which you want to assign view objects. In the right pane, select the Unassigned Objects tab. The list of objects that is displayed varies depending on the view type. From the Filter drop-down list, select the user-defined filter that you want to delete. If you have selected a default filter, the Delete Filter icon is disabled.

Chapter

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

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, you can view detailed information about your NetBackup environment including jobs, services, policies, media, devices, hosts, and alerts. Note that OpsCenter or OpsCenter Analytics can only monitor and manage NetBackup. It cannot monitor or manage other products like Symantec NetBackup PureDisk, Symantec Enterprise Vault etc.

Controlling the scope of Monitor views

The content that is shown in the Monitor views is based on your current View pane selection. You can select the following default option from the View pane:
ALL MASTER SERVERS Select ALL MASTER SERVERS to view information for all the NetBackup servers in your environment.

In addition to using the default view i.e. ALL MASTER SERVERS, you can also create your own views from Settings > Views or by using Java View Builder. For example, you can create a view like Geography to view details about master servers in a particular region like Europe. More information about how to create views by using the Settings > Views control is available. See About OpsCenter views on page 409. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. Use the following procedure to view details of all master servers or specific master servers.

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.

To view details of specific master servers

1 2

In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane. Deselect the checkbox next to ALL MASTER SERVERS and select the specific master servers from the list of master servers. Ensure that other master servers are unchecked. Click Apply Selection.

See About time frame selection on page 426.

About time frame selection

You can also view data for the last 24, 48, or 72 hours for some of the Monitor views. Click Last 24 Hours, Last 48 Hours, or Last 72 Hours respectively. These options are located on the top-right corner of specific Monitor views. Note that by default, data for the last 24 hours is shown in these views. You can control time frame selection for the following Monitor views:

Monitor > Overview (Job Summary by State, Job Summary by Exit Status, Top 7 Policies by Failed Jobs, Top 7 Job Error Log Summary, and Alert Summary by Severity sections) Monitor > Jobs Monitor > Alerts Monitor > Policies (Summary View)

In addition, you can also customize the time frame selection by clicking Customize and specifying an absolute time frame or relative time frame. Using the Customize option, you can view data for any time frame. The Customize option is located on the top-right corner of specific Monitor views. 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.

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 gives an overview of your NetBackup environment. This view contains the different sections which display specific information about your NetBackup environment. From this view, you can use links to drill down and access detailed information about many aspects of your NetBackup environment. Pie charts for most monitoring categories appear. The pie segments are also links to more details for the monitoring category. The following sections describe the Overview subtab in detail:

Viewing the Job Summary by State 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. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. A pie chart with different colors represents the job distribution. Each color of the pie chart represents how jobs are distributed in your environment as per the job state in the selected time frame. You can also view the color code summary in this section to know the colors that represent different job states. Pointing on the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. For example, pointing on the yellow color in the pie chart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environment are in a queued state.

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, incomplete, queued, active jobs etc. To view the Job Summary by job state

1 2

In the OpsCenter console, select Monitor > Overview. In the Job Summary by State section, do either of the following:

Click the number of jobs (link) for a particular job state from the table. For example, click the number that is shown for Done jobs. Or Click a colored section of the pie chart that corresponds to a particular job state. For example, click the yellow section of the pie chart to view details for Queued 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. This information is shown in a pie chart as well as a table. A pie chart with different colors represents media distribution in this section. Each color of the pie chart represents how media are distributed in your environment as per the media status. You can also view the color code summary in this section to know the colors that represent different media status. 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. For example, pointing on the red color in the pie chart shows that four media or 2% media in your environment are frozen. You can drill down from this section to see details for media with different status like details for frozen and active media. To view media by media status

1 2

In the OpsCenter console, select Monitor > Overview. In the Media Summary by Status section, do either of the following:

Click the number of media (link) for a particular media status from the table. For example, click the number for Frozen media. Or Click a colored section of the pie chart that corresponds to a particular media status. For example, click the red section of the pie chart to view details for Frozen media.

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. The content that is shown in this section is based on the current View pane selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. The table that appears in the section lists the top seven exit status codes responsible for maximum job failure. The table also lists the number of failed jobs for each exit status in the selected time frame. Note that the failed jobs that are shown in the Failed Job Count column are arranged in descending order in the table. By viewing this section, you can quickly analyze the reasons behind maximum job failures in your environment.

Viewing the Services Summary

The Services Summary section provides a high-level view that shows the total number of running and stopped NetBackup services for the current View pane selection. The total number of running and stopped NetBackup services are shown in a table. You can drill down from the links in this table to see details for running or stopped services. To view running or stopped services

1 2

In the OpsCenter console, select Monitor > Overview. In the Service Summary section, click the number that is shown in the Service Count column of the table. For example, click the number that is shown for Running services to view details for the services that are running.

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

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. You can also see details of the clients that do not have a backup policy configured for them. To view all master servers

1 2

In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Total column.

To view the master servers that are connected

1 2

In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Connected column.

To view details of the master servers that are not connected

1 2

In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Not Connected column.

To view details of the clients that are at risk

1 2

In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Clients at Risk column.

Viewing the Job Summary by Exit Status

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. This information is shown in a pie chart as well as a table. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. A pie chart with different colors represents the job distribution by exit status in the selected time frame. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. You can also view the color code summary in this section to know the colors that represent different exit status. Putting your pointer over the pie chart shows the total number and percentage of successful, partially successful, and failed jobs in your NetBackup environment. For example, pointing to the red color in the pie chart shows that in the last 24 hours, 72 jobs, or 42% jobs in your environment failed. This

Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab

431

information is also listed in a tabular format. In addition, a table also shows the amount of data that has been backed up for the selected view and time frame. You can drill down from this section to see details for failed, successful, or partially successful jobs. To view jobs by exit status

1 2 3

In the OpsCenter console, select Monitor > Overview. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Exit Status section, do either of the following:

Click the number of jobs (link) corresponding to a particular exit status from the table. Or Click a colored section of the pie chart that corresponds to a particular exit status. For example, click the red section of the pie chart to view details for failed jobs.

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. This information is shown in a pie chart as well as a table. Note: For 7.0.1 and 7.1 master servers, the Drive Summary by Status section does not show the drives that are disabled or unreachable. A pie chart with different colors represents the distribution of drives by drive status in the selected time frame. Each color of the pie chart represents how drives are distributed in your environment as per the drive status. You can also view the color code summary in this section to know the colors that represent different exit status. 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, pointing to the green color in the pie chart shows that 5 drives or 100% drives in your environment are up. You can drill down from this section to see details of all drives including up, down, or mixed drives. To view drives by drive status

1 2

In the OpsCenter console, select Monitor > Overview. In the Drive Summary by Status section, do either of the following:

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. For example, click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. For example, click the green section of the pie chart to view details for the drives that are up.

About Top 7 Policies by Failed Jobs section

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

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. This information is shown in a pie chart as well as a table. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. A pie chart with different colors represents the alert distribution by severity in this section. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. You can also view the color code summary in this section to know the colors that represent different severity. Moving your pointer over the pie chart gives the number and percentage of alerts with a particular severity in your NetBackup environment. For example, pointing to the green color in the pie chart shows that in the last 24 hours, 200 alerts, or 17% alerts in your environment are critical. You can drill down from this section to see details for alert categories.

Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs

433

To view alerts by severity

1 2

In the OpsCenter console, select Monitor > Overview. In the Alert Summary by Severity section, do either of the following:

Click the number of alerts (link) for a particular alert severity from the table. For example, click the number that is shown for Critical alerts. Or Click a colored section of the pie chart that corresponds to a particular alert severity. For example, click the red section of the pie chart to view details for Critical alerts.

About monitoring NetBackup jobs

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

Note: You can only view jobs data for the

last 30 days from the List View. See Monitor > Jobs List View options on page 434. Summary View The Summary View contains the different sections which show the NetBackup job distribution by exit status, job state, and job type based on the current View pane and time frame selection. This information is shown in pie charts and tables. See About using the Summary View for monitoring jobs on page 442.

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.

Note: You can only view jobs data for the

last 30 days from the Hierarchical View. See About using the Hierarchical View for monitoring jobs on page 447.

Note: You can select these views from the drop-down list. The drop-down list is located at the top-right corner of the page.

Monitor > Jobs List View options

This view is displayed when you select Monitor > Jobs. The List View is shown by default. This view displays detailed information for jobs for the current View Pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. Note: You can only view jobs data for the last 30 days from the List View. The table that appears in this view shows the following columns by default: Table 7-1 Option
Job ID

Monitor > Jobs List View options Description

This column shows the unique ID associated with the job (link). This column shows the name of the master server (link) associated with the job. You can click the link to view details for the master server. This column lists the job type like whether the job is a DB Backup or an Image Cleanup job. This column lists the current NetBackup job state like whether the job is Queued, Waiting for Retry, Done etc. Exit status of the job. The link provides status description and details on troubleshooting in case it failed.

Master Server

Type

State

Status

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. This column lists the name of the client on which the job is run. This column lists the date, time, and year when the job started. This column lists the time that is taken by the job. The Elapsed Time is the difference between End Time and Start Time values. For a running job, Elapsed Time is the difference between the current time and Start time.

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.) End Time This column lists the date, time, and year when the job ended. This column lists the size of the job. This column lists the number of files that have been backed up by this job. This column lists the percentage of job that has been completed.

Job Size Files

% Complete

Not all columns are displayed in the table by default. More columns can be added to your view by clicking the Table Settings icon. The Table Settings icon is located on the top-right corner of the table. The following columns are not displayed in the table by default:.

Schedule Source Media Server Destination Media Server Destination Storage Unit Attempt Operation PID

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71. All the details that are associated with a job can be viewed from the Details pane. The Details pane is located at the bottom of the Monitor > Jobs view. The Details pane has the following tabs:

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. It also includes the contents of all the available columns that can be viewed from the table. The Attempts tab shows details of the attempts that have been made to complete a job. The File List tab shows the files that have been backed up by the job and also their location.

Attempts

File List

About monitoring jobs using the List View

The following topics provide more information about monitoring jobs using the List View. See Viewing the details for a single NetBackup job on page 437. See Viewing the details for a master server associated with a job on page 438. See Viewing policy information for a job on page 438. See Filtering on NetBackup job state on page 438. See Controlling NetBackup jobs on page 439. See Reconciling NetBackup jobs on page 440. See Changing the job priority on page 441. See Exporting NetBackup job logs on page 442.

Viewing the details for a single NetBackup job

All the details that are associated with a job can be viewed from the Details pane. The Details pane is located at the bottom of the Monitor > Jobs view. The Details pane has the following tabs:
General The General tab of the Details pane displays all information available for the job. It also includes the contents of all the available columns that can be viewed from the table.

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. The File List tab shows the files that have been backed up by the job and also their location.

File List

To view details for a single NetBackup job

1 2

In the OpsCenter console, select Monitor > Jobs. Click the ID (link) for a job from the Job ID column of the table. View the job details in the Details pane

Viewing the details for a master server associated with a job

Use the following procedure to view the details for a master server that is associated with a job. To view details for the master server that is associated with a job

1 2

In the OpsCenter console, select Monitor > Jobs. Click the server name (link) associated with the job in the Master Server column of the table. The details of the master server are shown on a separate page. You can also enable or disable data collection for the master server from this page.

Viewing policy information for a job

Use the following procedure to view the details for the policy that is associated with a job. To view policy information for a job

1 2 3

In the OpsCenter console, select Monitor > Jobs. Click the policy name (link) for the job in the Policy column of the table. A separate page appears that shows policy information on four tabs. See Monitor > Policies page on page 457.

Filtering on NetBackup job state

You can filter by using any of the built-in job filters. These filters are available from the drop-down list which is present on top of the table. The built-in job filters are the following:

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. Select this filter to view only active jobs Select this filter to view only queued jobs. Select this filter to view only Done jobs. Select this filter to view the jobs that have been suspended. Select this filter to view the jobs that are waiting for retry. Select this filter to view the jobs that are incomplete. Select this filter to view the jobs that have been canceled. Select this filter to view the jobs that are undefined. Select this filter to view the jobs that are successful. Select this filter to view the jobs that are partially successful. Select this filter to view the jobs that failed.

Waiting for Retry Jobs

Incomplete Jobs

Canceled Jobs

Undefined Jobs

Successful Jobs

Partially Successful Jobs

Failed Jobs

In addition to using the built-in filters, you can also create your own custom filters. See Using filters to customize your views on page 74. To filter details by job state

1 2

Select Monitor > Jobs. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Controlling NetBackup jobs

Use the following procedure to cancel, suspend, resume, or restart a job. Before you perform these tasks, manually refresh your Web browser to obtain an updated view for all jobs. Note: These tasks are not visible if you log on with an Analyst or a Reporter role.

440

Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs

To control a job

1 2 3 4

In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select a job from the table. You may select one or more jobs. Click Cancel, Restart, Resume, Suspend. These options are located on top of the table. The OpsCenter console may take some time to show the updated status once you perform the tasks.

Reconciling NetBackup jobs

You can use the Reconcile option to prevent the jobs that failed due to reasons like user terminating a job, host cannot be reached etc. from being billed. By using the Reconcile option and selecting a reason, you can let your service provider know not to bill you for these jobs as these jobs failed due to specific issues at your end. Note: The Reconcile option is disabled in the unlicensed version (Symantec OpsCenter). Before you perform this task, manually refresh your Web browser to obtain an updated view for all jobs To reconcile NetBackup jobs

1 2 3 4 5

In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select a job from the table. You can select one or more jobs. From the More drop-down list, select Reconcile. In the Reconcile Jobs dialog box, select a reason for reconciling the job from the drop-down list. Note that you can select Un-Reconcile from the drop-down list to undo a reconciliation.

Click OK.

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. Priority can be changed only for jobs from the master servers that are running NetBackup 6.5.2 or higher versions.

To change the job priority

1 2 3 4 5 6 7

In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select an active job or a queued job from the table. From the More drop-down list, select Change Job Priority. In the Change Priority dialog box, set the job priority to a particular value. You can also increment or decrement the job priority. Click OK. Click Finish. The OpsCenter console may take some time to show the updated status once you perform this task.

Change Job Priority dialog box options

A description of the Change Job Priority dialog box options follows in the table. 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. 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.

See Changing the job priority on page 441.

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 view or save the exported log files in an Excel format. Note: The Export Job Logs option is not visible if you log on with an Analyst or a Reporter role.

Note: Logs are not available for all job types. Before exporting a log file, ensure that the NetBackup master server is Connected and the selected job logs are enabled. To export the NetBackup log files for a job

1 2 3

In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select a job from the table. You can export only one job log at a time.

4 5

From the More drop-down list, select Export Job Logs. Click Open or Save from the dialog box to view or save the log file in an Excel format.

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. The drop-down list is located at the top-right corner of the page. The content that is shown in the Summary View is based on the current View Pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. The Summary View contains the different sections which display specific information about NetBackup jobs. These sections show NetBackup job information in a table as well as a pie chart. The table and the pie charts include links to filtered detail views. You can use these links to drill down and access detailed information about NetBackup jobs.

Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs

443

Note: If you uncheck the Allow Multiple Selection In View Pane option, a Group Component Summary table is displayed when you access the Summary View for Monitor > Jobs. The Group Component Summary table displays information about immediate NetBackup constituents of the view or node (group) that you selected in the View pane. 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. The data that is shown in this view is based on the current View pane and time frame selection. This information is shown in a pie chart as well as a table. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. A pie chart with different colors represents the job distribution by exit status in this section. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. You can also view the color code summary in this section to know the colors that represent different exit status. Moving your pointer over the pie chart gives the number and percentage of jobs with a particular exit status in your NetBackup environment. For example, pointing your cursor to the red color in the pie chart shows that in the last 24 hours, 72 jobs, or 42% jobs in your environment failed. You can drill down from this section to see details for successful, partially successful, and failed jobs. To view jobs by exit status

1 2 3

In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Exit Status section, do either of the following:

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. Or Click a colored section of the pie chart that corresponds to a particular exit status. For example, click the red section of the pie chart to view details for failed jobs.

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. This information is shown in a pie chart as well as a table. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. A pie chart with different colors represents the job distribution by job state. Each color of the pie chart represents how jobs are distributed in your environment as per the job state. You can also view the color code summary in this section to know the colors that represent different job states. Moving your cursor over the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. For example, pointing to the yellow color in the pie chart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environment are in a queued state. You can drill down from this section to see details for the jobs that failed, the jobs that are waiting for retry, queued or active jobs, and so on. To view jobs by job state

1 2 3

In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by State section, do either of the following:

Click the number of jobs (link) in a particular job state from the table. For example, click the number that is shown for Done jobs. Or Click a colored section of the pie chart that corresponds to a particular job state. For example, click the yellow section of the pie chart to view details for Queued 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. This information is shown in a pie chart as well as a table. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. A pie chart with different colors represents the job distribution by job type in this section. Each color of the pie chart represents how jobs are distributed in your environment as per the job type. You can also view the color code summary in this section to know the colors that represent different job types. Moving your cursor over the pie chart gives the number and percentage of jobs of a particular job type in your NetBackup environment. For example, pointing to the red color in the pie chart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environment are DBBackup jobs. You can drill down from this section to see details for different job types like DBBackup, Image Cleanup etc. To view jobs by job type

1 2 3

In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Type section, do either of the following:

Click the number of jobs (link) corresponding to a particular job type from the table. For example, click the number that is shown for DBBackup jobs. Or Click a colored section of the pie chart that corresponds to a particular job type. For example, click the red section of the pie chart to view details 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 can view the Group Component Summary table in the Summary View for Monitor > Jobs. The Group Component Summary table is displayed at the bottom of the Summary View for Monitor > Jobs. The Group Component Summary table was also displayed in NOM earlier. You must select a group (view or node) from the View pane to see data in the Group Component Summary table. You do not see any data in the Group

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. More details about nodes and view objects is available. See About nodes and objects on page 414. 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. For example if you select the ALL MASTER SERVERS view, the Group Component Summary table displays job summary for each master server. If you select a view that contains multiple nodes, a job summary of the nodes (and not the view objects for each node) is displayed. Note: OpsCenter or OpsCenter Analytics monitors only NetBackup. Hence any other servers (like BE, PD, 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. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. Table 7-4 explains the information that is displayed in the Group Component Summary table. Table 7-4 Column
Name Total

Columns and descriptions in the Group Component Summary table Description

Name of the node or view object. 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 all the jobs. Number of successful jobs (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about successful jobs. Number of partially successful jobs (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about the partially successful jobs.

Successful

Partially Successful

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. Click the link to view detailed information about the failed jobs. Data that is backed up for the specific node or view object in the selected time frame. 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 active jobs. Number of queued 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. Click the link to view detailed information about the suspended jobs. Number of incomplete jobs (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about the incomplete 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 undefined jobs. 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 jobs that are waiting for retry.

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. The data that is shown in this view is based on the

448

Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs

current View pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. Note: You can only view jobs data for the last 30 days from the Hierarchical View. See Controlling the scope of Monitor views on page 425. In the Hierarchical View, all related jobs can be grouped and you can see all parent-child jobs in a hierarchical fashion. You can view details of only the top level, parent job in this view with the ability to expand and drill into the details of child jobs if there are failures. The Hierarchical View shows details of all jobs and also highlights the parent-child relationship between jobs wherever applicable. All parent jobs have a +sign before the job ID. You can click the + sign to see all child jobs. A child job is indented to the right-hand side in the Job ID column. If some of the child jobs are parent jobs, then + sign also appears before the job ID of the child job. However, if a job does not have a relationship with any other job (it is neither a parent nor a child job), it is represented only by its job ID in the Job ID column. Neither is there a + sign before the job ID of such a job nor this job is indented to the right-hand side. Note the following things about the related jobs that are shown in the Hierarchical View:

The filters are applied only to parent jobs. The filters are not applied to child jobs. For example, if you apply the Partially Successful Jobs filter, child jobs are not considered at all. Only parent jobs or unrelated jobs (jobs that are not related to any other job) with partially successful status are considered. The sorting feature in the Hierarchical View applies to both parent jobs and child jobs. When you expand a parent job, the current selected sort order is applied to child jobs. All tasks that apply to the parent job are also applicable to its child jobs.

Viewing the details for a single NetBackup job

All the details that are associated with a job can be viewed from the Details pane. The Details pane is located at the bottom of the Monitor > Jobs view. The Details pane has the following tabs:
General The General tab of the Details pane displays all information available for the job. It also includes the contents of all the available columns that can be viewed from the table.

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. The File List tab shows the files that have been backed up by the job and also their location.

File List

To view details for a single NetBackup job

1 2 3 4

In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view. Click the ID (link) for a job from the Job ID column of the table. View the job details in the Details pane.

Viewing the details for a master server associated with a job

Use the following procedure to view the details for a master server that is associated with a job. To view the details for the master server that is associated with a job

1 2 3

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

Viewing policy information for a job

Use the following procedure to view the details for the policy that is associated with a job. Note: You can also view policy information from the List View. To view policy information for a job

1 2

In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view.

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. A separate page appears that shows policy information on four tabs. See Monitor > Policies page on page 457.

Filtering on NetBackup job state

You can filter by using any of the following built-in job filters. These filters are available from the drop-down list which is present on top of the table. The built-in job filters are the following:
All Jobs (default filter) Active Jobs Queued Jobs Done Jobs Suspended Jobs Select this filter to view details of all the jobs. Select this filter to view only active jobs Select this filter to view only queued jobs. Select this filter to view only Done jobs. Select this filter to view the jobs that have been suspended. Select this filter to view the jobs that are waiting for retry. Select this filter to view the jobs that are incomplete. Select this filter to view the jobs that are undefined. Select this filter to view the jobs that have been canceled. Select this filter to view the jobs that are successful. Select this filter to view the jobs that are partially successful. Select this filter to view the jobs that failed.

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, you can also create your own custom filters. See Using filters to customize your views on page 74.

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

451

To filter details by job state

1 2 3

In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Monitor > Services view

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

Service Type

Note: The status for some services may

show as Stopped on the Monitor > Services page in the OpsCenter console. The license for these services is either not installed or configured for a specific media or master server.

You can perform the following tasks from this view:

452

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

Use filters to view specific services

See Filtering on NetBackup service type on page 452. See Controlling NetBackup services on page 452.

Control NetBackup services

Filtering on NetBackup service type

You can filter by using any of the four built-in filters. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Services (default filter) Select this filter to view details of all the services. Select this filter to view details of the services that have been stopped. Select this filter to view details of running services. Select this filter to view details of all other services like Not Licensed, Unknown (not recognized by OpsCenter), or Not Applicable (some services may not be applicable to earlier versions).

Stopped Services

Running Services

Other Services

In addition to using the built-in filters, you can also create your own custom filters. See Using filters to customize your views on page 74. Use the following procedure to view details by type of service. To view details by type of service

1 2

In the OpsCenter console, select Monitor > Services. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Controlling NetBackup services

Under certain circumstances there may be issues among multiple OpsCenter users. For instance, one OpsCenter user stops a service while another user tries to start the same service.

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

453

Note: NetBackup service layer (nbsl) cannot be controlled from OpsCenter. To control a service

1 2 3 4

Refresh your Web browser to obtain an updated state for all services. In the OpsCenter console, select Monitor > Services. Select a service from the table. You can select one or more services. Click Start, Stop, or Restart. Note that these tasks are located on top of the table. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. The OpsCenter console may take some time to show the updated status once you perform these tasks. Stop, Running, or Restart Pending appears in the Status column until the selected action completes. If you start or stop a service that has a dependency on another service, NetBackup ensures that any dependent services are also started or stopped.

About monitoring NetBackup policies

The Monitor > Policies view provides details of NetBackup policies. 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. This view shows detailed information about NetBackup policies based on the current View pane selection. See Monitor > Policies List View on page 454. 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. These sections show specific policy information in a table as well as a pie chart. See Monitor > Policies Summary View on page 460.

454

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

Note: You can select these views from the drop-down list. The drop-down list is located at the top-right corner of the page. See About using the List View to monitor NetBackup policies on page 456. See Filtering on NetBackup policy type on page 456. See Viewing details for a single NetBackup policy on page 458. See Viewing details for a single NetBackup policy on page 458. See Viewing details for a single NetBackup policy on page 458. See Viewing details for a single NetBackup policy on page 458. See Viewing details for a single NetBackup policy on page 458. See Viewing details for a single NetBackup policy on page 458.

Monitor > Policies List View

This view is displayed when you select Monitor > Policies. This view contains detailed information about policies. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. The table that appears in this view has the following columns:
Name Name of the policy. Click the link to view details about the policy. Name of the master server that is associated with the policy. Click the link to view details of master server. This column is the policy type. Usually, the Policy type determines the type of clients that can be backed up by this policy. Example: DB2, NBU-Catalog, Oracle, Sybase, Vault etc. Storage that is associated with the policy. Click the link to view details for storage. Volume pool that is associated with the policy. Click the link to view details of volume pool.

Master Server

Type

Storage

Volume Pool

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

455

CheckPoint Interval

Interval (in minutes) between two checkpoints in NetBackup. The total number of jobs that are associated with the policy. Priority that you have defined for the policy. Zero means the lowest priority. This column determines whether the policy is Active or not.

Jobs/Policy

Priority

Active

Not all of the available columns appear initially in this view. The following columns do not appear, but can be added to your view by clicking the Table Settings icon:

Data Classification Effective Date Compression Encryption Block Level Increments Allow Multiple Data Streams Offhost Follow NFS Cross Mount Points Individual File Restore From Raw True Image Recovery Collect Disaster Recovery Information Collect Bare Metal Restore Information Snapshot Backups Alternate Client Data Mover Virtual Machine Proxy Snapshot Method Keyword Phrase Policy Domain Name

456

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 71.

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. See Viewing details for a single NetBackup policy on page 458. See Viewing the details for a master server associated with a policy on page 458. See Viewing the details for a volume pool associated with a policy on page 458. See Activating or deactivating a job policy on page 459. See Starting a manual backup on page 459. See Viewing the history for a single job policy on page 460.

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. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Policies (default filter) Select this filter to view details of all NetBackup policies. Select this filter to view details of the policies that are active.

Active Policies

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 policies that apply to Windows clients. Select this filter to view details of catalog policies. Select this filter to view details of Standard policies. Select this filter to view details of all other policies like DB2 policies, SAP policies, OS2 policies etc.

Windows Policies

Catalog Policies

Standard Policies

Other Policies

In addition to using the built-in filters, you can also create your own custom filters. See Using filters to customize your views on page 74. Use the following procedure to view details by type of policy. To filters details by type of policy

1 2

In the OpsCenter console, select Monitor > Policies. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Monitor > Policies page

There are four tabs in the Details pane on the Monitor > Policies page. Table 7-5 Tab
General

Monitor > Policies page tabs Description

The General tab of the Details pane displays all information available for the policy. It also includes contents of all the columns that can be viewed from the table. You can also click the master server name (link) to get details of the master server.

Schedules

The Schedules tab displays details of the schedules that are associated with the policy. The Clients tab shows details of clients to be backed up by the policy.

Clients

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.

Viewing details for a single NetBackup policy

All the details that are associated with a policy can be viewed from the Details pane. The Details pane is located at the bottom of the Monitor > Jobs view. The Details pane has four tabs. See Monitor > Policies page on page 457. To view details for a single NetBackup policy

1 2 3

In the OpsCenter console, select Monitor > Policies. Click the name (link) for a policy from the Name column of the table. View the policy details in the Details pane.

Viewing the details for a master server associated with a policy

Use the following procedure to view the details for a master server that is associated with a policy. To view the details for a master server that is associated with a policy

1 2

In the OpsCenter console, select Monitor > Policies. Click the server name (link) associated with the policy from the Master Server column of the table. The details of the master server are shown on a separate page. You can also enable or disable data collection for the master server from this page.

Viewing the details for a volume pool associated with a policy

Use the following procedure to view the details for a volume pool that is associated with a policy. To view the details for a volume pool that is associated with a policy

1 2

In the OpsCenter console, select Monitor > Policies. Click the volume pool name (link) associated with the policy from the Volume Pool column in the table. The details of the volume pool are shown on a separate page.

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. Before you perform these tasks, manually refresh your Web browser to obtain an updated view of all policies. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To activate or deactivate a policy

1 2 3

In the OpsCenter console, select Monitor > Policies. Select a job policy from the table. Click Activate or Deactivate. Note that these options are located on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.

Starting a manual backup

Use the following procedure to start a manual backup. Before you perform this task, manually refresh your Web browser to obtain an updated view of all policies. The OpsCenter console may take some time to show the updated status once you perform this task. Note: This task is not visible if you log on with an Analyst or a Reporter role. To start a manual backup

1 2 3 4

In the OpsCenter console, select Monitor > Policies. Select a policy from the table. You can select only one policy and it must be an active policy. Click Manual Backup. Note that this option is located on top of the table. You can select a schedule and a client from the drop-down lists for the backup, or only select a schedule or a client. If you do not select a schedule, NetBackup uses the schedule with the highest retention level. If you do not select a client, NetBackup backs up all scheduled clients.

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. Note: This task is not visible if you log on with an Analyst or a Reporter role. To view the history for a policy

1 2 3 4

In the OpsCenter console, select Monitor > Policies. Select a job policy from the table. Click View History. Note that this option is located on top of the table. The Compare Policies tab displays the policy versions. You must select two versions from the Retirement Date column to compare versions. The changes are highlighted in red color. To view only the differences between the versions, click the View Differences tab.

Monitor > Policies Summary View

This view is displayed when you select Monitor > Policies and then select Summary View from the drop-down list. The drop-down list is located at the top-right corner of the page. This view contains detailed information about policies. The content that is shown in the Summary View is based on the current View pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. The Summary View contains the different sections which display specific information about NetBackup policies. These sections show specific policy information in a table as well as a pie chart. The table and the pie charts include links to filtered detail views. You can use these links to drill down and access detailed information about NetBackup policies. The following sections describe this view in detail:

About Top 5 Policies by Data Backed up section About Top 7 Policies by Failed Jobs section About Top 7 Policies by No. of Jobs section

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

About Top 7 Policies by No. of Jobs section

The Top 7 Policies by No. of Jobs section lists seven policies which have the maximum number of jobs. This data is based on the current View pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours.

462

Monitoring NetBackup using Symantec OpsCenter Monitor > Services view

See Controlling the scope of Monitor views on page 425. The table that is shown in the section lists the policies which have maximum number of jobs. The table also shows the total number of jobs for each policy. Note that the total number of jobs for each policy (shown in Total Number of Jobs column) are arranged in descending order in the table. From this section, you can quickly view the policies which have the maximum number of jobs associated with them. See About Top 5 Policies by Data Backed up section on page 461. See About Top 7 Policies by Failed Jobs section on page 461.

About monitoring NetBackup media

The Monitor > Media view provides details of NetBackup media. You can use the following views to see details about NetBackup media:
List View The List View is shown by default when you select Monitor > Media. This view shows detailed information about NetBackup media for the current View pane selection. See Monitor > Media List View options on page 463. Summary View The Summary View displays the volume pool available for each master server for the current View pane selection. It also shows other media details that are associated with the master server like Frozen Media Count, Suspended Media Count etc. See Monitor > Media Summary View options on page 468. 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 using the Hierarchical View by Volume Pool for monitoring media on page 468.

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. See About using the Hierarchical View by Volume Group for monitoring media on page 470.

Note: You can select these views from the drop-down list. The drop-down list is located at the top-right corner of the page.

Monitor > Media List View options

This view is displayed when you select Monitor > Media. This view contains detailed information for media. This data is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. 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. Click the link to view details about the media. Name of the master server that is associated with the media. Click the link to view details of master server. Type of media like 8mm, 4mm etc. Specifies the robot type of the robot to inventory. Example: tl4, tl8 etc. Unique, logical identification number for the robot to inventory. Slot in the robot that contains the volume. The number of times that the volume has been mounted. The date when the volume was assigned for use.

Column Head/Option
Media ID

Master Server

Media Type Robot Type

Robot Number

Slot Mounts

Time Assigned

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. Zero (0) indicates unlimited mounts. Date when the images on the volume expire. The most recent time NetBackup used the volume for backups. Current media status like Frozen, Active etc. Capacity that has been used.

Column Head/Option
Max. Mounts

Data Expiration Last Written

Media Status Used Capacity

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:

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

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71.

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 Filtering on NetBackup media type on page 466. See Controlling media on page 467.

Control media

Viewing the details for NetBackup media

All the details that are associated with a media can be viewed from the Details pane. The Details pane is located at the bottom of the view.

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, select Monitor > Media. Click a drilldown link from the Media ID column. View the media properties from the Details pane. From the Details pane, you can also click the master server link to see details about the master server that is associated with the media.

Viewing the details for a master server associated with the media
Use the following procedure to view the details for a master server that is associated with a media. To view the details for a master server associated with a media

1 2

In the OpsCenter console, select Monitor > Media. Click the server name (link) associated with the media in the Master Server column of the table. The details of the master server are shown on a separate page.

Filtering on NetBackup media type

You can sort and filter this view to focus on the specific type of media that you want to see. For example, you can create and apply a filter that displays full media only. You can filter by using any of the built-in filters. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Media (default filter) Assigned Media Select this filter to view details of all media. Select this filter to view details of the media that have been assigned to an individual for further action. Select this filter to view details of the media that are unassigned. Select this filter to view details of the media that are frozen. Select this filter to view details of the media that are full.

Unassigned Media

Frozen Media

Full Media

Monitoring NetBackup using Symantec OpsCenter Controlling media

467

Suspended Media

Select this filter to view details of the media that are suspended. Select this filter to view details of all other media like Multi Retention Level media, BE media etc. Select this filter to view details of media with Active status. Select this filter to view details of cleaning media.

Other Media

Active Media

Cleaning Media

In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 74. Use the following procedure to view details by type of media. To filter details by type of media

1 2

In the OpsCenter console, select Monitor > Media. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Controlling media
Use the following procedure to freeze, unfreeze, suspend, or unsuspend specific media. Note that to perform these tasks the media must be assigned to NetBackup. The media is assigned if there is a date in the Time Assigned column. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To perform media tasks

1 2 3

In the OpsCenter console, select Monitor > Media. Select a media ID from the table (use the check box). Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these options are present on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.

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. The drop-down list is located at the top-right corner of the page. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. The table that appears in this view displays the volume pool available for each master server. It also shows other media details that are associated with the master server like Frozen Media Count, Suspended Media Count etc. The following columns are shown in the table: 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. Total number of the suspended media that is associated with the master server. Total number of the full media that are associated with the master server. Total number of active media that are associated with the master server. Total number of all other media like Multi Retention Level media, BE media etc. that are associated with the master server . Total number of the media that are available for 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. 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. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. The Hierarchical View by Volume Pool shows details of all media and also groups media by volume pool. Each volume pool that is shown in the Media ID column has a +sign before it. You can expand a volume pool to see all media that are a part of this volume pool. Note that the media are indented to the right-hand side in the Media ID column. The sorting feature in this view applies only to media in the volume pool. When you expand a volume pool, the current selected sort order is applied to media in the pool. The following tasks can be performed from this view:
View the details for volume pool See Viewing the details for volume pool on page 469.

View details for the media that are a part of See Viewing the details for media a specific volume pool on page 469. Control media See Controlling media on page 470.

Viewing the details for volume pool

Use the following procedure to view the details for a volume pool. To view details for a volume pool

1 2 3

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

Viewing the details for media

Use the following procedure to view details for the media that are part of a specific volume pool.

470

Monitoring NetBackup using Symantec OpsCenter Controlling media

To view the details for media

1 2 3

In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Pool from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume pool from the Media ID column. This column shows the media that are a part of the volume pool. Note that the media are indented to the right-hand side Click the media ID (link). Details for the media are shown in the General tab at the bottom of the view.

Controlling media
Use the following procedure to freeze, unfreeze, suspend, or unsuspend specific media. Note that to perform these tasks the media must be assigned to NetBackup. The media is assigned if there is a date in the Time Assigned column. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To perform media tasks

1 2 3

In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Pool from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume pool from the Media ID column. This view shows the media that are a part of the volume pool. Note that the media are indented to the right-hand side Select a media ID (use the check box). Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these tasks are present on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.

4 5

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. The drop-down

Monitoring NetBackup using Symantec OpsCenter Viewing the details for a volume group

471

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

View details for the media that are part of a See Viewing the details for media specific volume group on page 471. Control media See Controlling media in OpsCenter on page 472.

Viewing the details for a volume group

Use the following procedure to view the details for a specific volume group. To view details for a volume group

1 2 3

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

Viewing the details for media

Use the following procedure to view details for media that are part of a specific volume group.

472

Monitoring NetBackup using Symantec OpsCenter Controlling media in OpsCenter

To view the details for media

1 2 3

In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Group from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume group from the Media ID column. This view shows the media that are a part of the volume group. Note that the media are indented to the right-hand side Click the media ID (link). Details for the media are shown in the General tab at the bottom of the view.

Controlling media in OpsCenter

Use the following procedure to freeze, unfreeze, suspend, or unsuspend specific media. Note that to perform these tasks the media must be assigned to NetBackup. The media is assigned if there is a date in the Time Assigned column. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To perform media tasks

1 2 3

In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Group from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume group from the Media ID column. This view shows the media that are a part of the volume group. Note that the media are indented to the right-hand side Select a media ID (use the check box). Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these options are present on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.

4 5

Monitoring NetBackup devices

This view is displayed when you select Monitor > Devices. This view contains the following two tabs:

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 contents of the Drives tab are shown by default. This view displays the current drive status information based on the current View pane selection. See Monitor > Devices > Drives List View options on page 473. See Monitor > Devices > Drives Summary View on page 477.

Disk Pools

This view displays detailed information about the disk pools that are configured for use by NetBackup based on the current View pane selection. See Monitor > Devices > Disk Pools options on page 478.

Monitor > Devices > Drives List View options

This view is displayed when you select Monitor > Devices > Drives. This view shows the current drive status information. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. Note: For 7.0.1 and 7.1 master servers, the List View does not show a drive that is unreachable or disabled. Similarly if one of the paths for a drive is unreachable or disabled, it is not shown in the Paths tab that appears in the List View. The table that appears in this view shows the following information: Table 7-8 Drives List View options Description
The name that is assigned to the drive when it was added to NetBackup. The name of the device host where the drive is connected. Name of the master server that is associated with the drive. Type of drive like 4mm, 8mm etc.

Option/Column Head
Drive Name

Device Host Master Server Drive Type

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.

Option/Column Head
Robot Type

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:

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

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71.

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. See Viewing the details for a master server associated with a drive on page 476. See Filtering on NetBackup drive category on page 476. See Controlling drives on page 477.

View the details for a master server that is associated with a drive Use filters to view specific drives

Control drives

Viewing the details for a single drive

All the details that are associated with a drive can be viewed from the Details pane. The Details pane is located at the bottom of the view. To view the details for a single drive

1 2

Select Monitor > Devices > Drives. The List View is shown by default. Click the drilldown link from the Drive Name column. The drive information can be viewed from the General and Paths tab of the Details pane. From the General tab, you can also click the master server link to see details about the master server that is associated with the drive.

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. To view the details for a master server associated with a drive

1 2

Select Monitor > Devices > Drives. The List View is shown by default. Click the drilldown link from the Master Server column. The master server information can be viewed from a separate page.

Filtering on NetBackup drive category

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

Up Drives

Down Drives

Mixed Drives

In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 74. Use the following procedure to view details by type of drives.

Monitoring NetBackup using Symantec OpsCenter Controlling drives

477

To filter details by type of drives

1 2

In the OpsCenter console, select Monitor > Devices > Drives. Ensure that List View is selected in the drop-down list. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Controlling drives
See the NetBackup Administrator's Guide, Volume I for information on drive states and how to control drives. Before you perform these tasks, manually refresh your Web browser to obtain an updated view of all drives. When you refresh, you also ensure that the drive is not involved in any tasks by other users. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To control drives

1 2 3

In the OpsCenter console, select Monitor > Devices > Drives. The List View is displayed by default. Select a drive from the Drive Name column in the table. Click Up, Down, or Reset. Note that these options are located on top of the drive details table. The OpsCenter console may take some time to show the updated status once you perform these tasks.

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. The drop-down list is located at the top-right corner of the page. The Summary view contains the following section: See Viewing the Drive Summary by Status on page 478.

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. This information is shown in a pie chart as well as a table. Note: For 7.0.1 and 7.1 master servers, the Drive Summary by Status section does not show the drives that are disabled or unreachable. Each color of the pie chart represents how drives are distributed in your environment as per the drive status. You can also view the color code summary in this section to know the colors that represent different exit status. Moving your mouse over the pie chart shows the number and percentage of drives with up or down status in your NetBackup environment. For example, pointing to the green color in the pie chart shows that 5 drives or 100% drives in your environment are up. Note: The Drive Summary by Status section can also be viewed from Monitor > Overview. You can drill down from this section to see details of the drives that are up or down. To view drives by drive status

1 2 3

In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. The drop-down list is located at the top-right corner of the page. In the Drive Summary by Status section, do either of the following:

Click the number of drives (link) for a particular drive status from the table. For example, click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. For example, click the green section of the pie chart to view details for the drives that are up.

Monitor > Devices > Disk Pools options

This view is displayed when you select Monitor > Devices > Disk Pools. This view displays detailed information about the disk pools that are configured for use by

Monitoring NetBackup using Symantec OpsCenter Monitor > Devices > Disk Pools options

479

NetBackup. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. The table that appears in this view shows the following information:
Name Server Type Name of the disk pool The storage server type. For OpenStorage, the server type depends on the vendor name. Number of disk volumes in the disk pool. The amount of storage space in use. The total raw, unformatted size of the storage in the disk pool. The estimated amount of disk space available for storage after file metadata overhead is taken into account. The low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit.

Number of Volumes Used Capacity Raw Size

Usable Size

Low Watermark (%)

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71. You can perform the following task from this view:

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.

Viewing the details for a single disk pool

All the details that are associated with a disk pool can be viewed from the Details pane. The Details pane is located at the bottom of the view. To view the details for a single disk pool

1 2

In the OpsCenter console, select Monitor > Devices > Disk Pools. Click the drilldown link from the Name column. The disk pool information can be viewed from the General and Disk Volume tab of the Details pane. From the General tab, you can also click the master server link to see details about the master server that is associated with the disk pool.

About monitoring NetBackup hosts

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

Monitoring NetBackup using Symantec OpsCenter Monitor > Hosts > Master Servers view

481

Monitor > Hosts > Master Servers view

This view shows details of master servers. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. 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. The display name that you have chosen for the master server. Operating system of the master server. Back up product from where the data is being collected like PureDisk, Backup Exec etc. The last time when OpsCenter successfully initiated contact with the master server. This does not necessarily represent the last time that OpsCenter collected information from the master server. Shows the current state of the master server like Connected, Not Connected etc.

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.

Filtering by NetBackup master server type and status

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

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. Select this filter to view details of those master servers that are connected. Select this filter to view details of those master servers that are partially connected. Select this filter to view details of those master servers that appear as not connected. Select this filter to view details of Windows servers. Select this filter to view details of Solaris servers. Select this filter to view details of Linux servers. Select this filter to view details of all other servers like AIX servers, HP-UX servers etc.

Connected Servers

Partially Connected Servers

Not Connected Servers

Windows Servers

Solaris Servers

Linux Servers

Other Servers

In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 74. Use the following procedure to view details by type of master server. To filter details by type of master server

1 2

In the OpsCenter console, select Monitor > Hosts > Master Server. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

Monitor > Hosts > Media Servers view

This view shows details of media servers. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. The table that appears in this view shows the following columns:

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.

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.

Viewing the details of a master server that is associated with a media server
Use the following procedure to view the details of a master server that is associated with a media server. To view the details of a master server that is associated with a media server

1 2

In the OpsCenter console, select Monitor > Hosts > Media Servers. Click the drilldown link from the Master Server column.

Monitor > Hosts > Clients view

This view shows details of NetBackup clients. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 425. 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. Name of the master server that is associated with the client. Operating system on the client like Linux, HP-UX etc. Hardware of the client computer like PC.

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. You can search for clients using absolute host names or substrings. 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.

Viewing the details for a single master server

All the details for a master server that is associated with a client can be viewed from the General tab. To view the details for a single master server

1 2

In the OpsCenter console, select Monitor > Hosts > Client. Click the drilldown link in the Master Server column.

About monitoring NetBackup alerts

The Monitor > Alerts view provides details of NetBackup alerts. The data that is shown in this view is based on the current View pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. Note: The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). You can use the following views to see NetBackup alert information:
List View The List View is shown by default when you select Monitor > Alerts. The List View shows active alerts by default. This view also lets you view detailed information about all NetBackup alerts and also filter, respond to alerts. See Monitor > Alerts List View on page 485.

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 Summary View shows how active alerts are distributed in your environment as per the alert severity. This information is shown in a pie chart as well as a table. See About using the Summary View for monitoring NetBackup alerts on page 491.

Monitor > Alerts List View

The List view is displayed when you select Monitor > Alerts. This view contains detailed information for alerts. This view provides tools to view and filter alerts, and to track user responses to alerts. The data that is shown in this view is based on the current View pane and time frame selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 425. Note: The List View displays active alerts by default (these are the alerts that have not been cleared). The table that appears in this view shows the following information: Table 7-12 Option
Alert ID Severity

Alerts List View options Description

Unique ID associated with each NetBackup alert. The severity of the alert. The severity type helps you determine how quickly you want to respond. Name of the policy that is associated with the alert. The alert condition that is used for the alert. Current status of the alert like Active, Cleared etc. Name of the individual to whom the alert has been assigned. Time, date, and year when the alert was raised. Time, date, and year when the alert was modified.

Alert Policy Alert Condition Status Assigned To Time Raised Last Update Time

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.

Not all of the available columns appear initially in this view. The Assignment State column does not appear, but can be added to your view by clicking the Table Settings icon. More information about how to customize tables and view specific columns is available. See About using tables on page 71.

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. See Viewing the details of the alert policy associated with an alert on page 487. See Filtering by alert type on page 487. See Responding to alerts on page 488.

View the details of an alert policy that is associated with the alert Use filters to view specific alerts Respond to alerts

Viewing the details for a single alert

All the details that are associated with an alert can be viewed from the Details pane. The Details pane is located at the bottom of the view. To view the details of a single alert

1 2

In the OpsCenter console, select Monitor > Alerts. Click a drill-down link from the Alert ID column. The alert details are shown under General and Comments tabs of the Details pane. In addition to the information that is shown in the table, the General tab also shows master server, policy name, job ID, and exit status information. The Comments tab shows comments on the alert (if any), the time these comments were given and the individual who last updated the alert.

See Viewing the details of the alert policy associated with an alert on page 487. See Filtering by alert type on page 487.

Monitoring NetBackup using Symantec OpsCenter Viewing the details of the alert policy associated with an alert

487

See Responding to alerts on page 488.

Viewing the details of the alert policy associated with an alert

Use the following procedure to view the details of the alert policy that is associated with an alert. To view the details of alert policy associated with the alert

1 2

In the OpsCenter console, select Monitor > Alerts. Click the drill-down link from the Alert Policy column.

See Viewing the details for a single alert on page 486. See Filtering by alert type on page 487. See Responding to alerts on page 488.

Filtering by alert type

Since the Monitor > Alerts view can include large numbers of alerts, a filter is available. You can use this filter to limit the types of alerts that appear. You can filter on various severity levels or status settings, which lets you focus on only the specific alerts that interest you. For example, you can create and apply a filter that only displays the alerts that are acknowledged. You can filter using any of the following nine built-in alert filters. These filters are available from the drop-down list which is present on top of the alert details table.
Active (default filter) Select this filter to view Active alerts. This filter does not include the alerts that have been cleared. Select this filter to only view the alerts whose severity is Critical. Select this filter to only view the alerts whose severity is Major. Select this filter to only view the alerts whose severity is Warning. Select this filter to only view the alerts whose severity is Informational.

Critical

Major

Warning

Informational

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. Select this filter to only view the alerts that have been assigned to other OpsCenter users. Select this filter to only view the alerts that have been acknowledged by an OpsCenter user. Select this filter to only view the alerts that have been cleared. More information on cleared alerts is available. See Responding to alerts on page 488.

Assigned

Acknowledged

Cleared

All Alerts

Select this filter to view the details of all alerts. This filter includes both active alerts and cleared alerts.

In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 74. Use the following procedure to view details by type of alerts. To filter details by type of alert

1 2

In the OpsCenter console, select Monitor > Alerts. Select a filter using the Filter drop-down list. For example, select All Alerts to view details of both active alerts and cleared alerts.

See Viewing the details for a single alert on page 486. See Viewing the details of the alert policy associated with an alert on page 487. See Responding to alerts on page 488.

Responding to alerts
You can manage OpsCenter alerts from the Monitor > Alerts view by adding comments or by assigning the alert to an individual for further review. You can also clear or acknowledge an alert. OpsCenter allows multiple users to process or take action on an alert. When you acknowledge an alert, you inform other users who see the alert that action on the alert occurred. If you clear an alert, you cannot perform any further activity on the alert (for example, assign or acknowledge). Cleared alerts do not appear in the alert view by default.

Monitoring NetBackup using Symantec OpsCenter Responding to alerts

489

Note: Under certain circumstances there may be issues among multiple OpsCenter users. For instance, an OpsCenter user comments on an alert while another OpsCenter user tries to clear the same alert. The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). Some alerts (for example, Drive is Down) are cleared automatically when the condition is resolved. You can view cleared alerts from Monitor > Alerts view (List View) by using the Cleared or All Alerts filter. See Filtering by alert type on page 487. 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

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. Any purged data is deleted permanently. This option is useful if you see OpsCenter performance degrade when there is a high number of alerts in the OpsCenter database. See Configuring the data purge period on the OpsCenter Server on page 309. To acknowledge an alert

1 2 3

In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click Acknowledge or Clear.

To add a comment for an alert

1 2 3

In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click Add Comment. You can add a comment as a reminder to yourself or for other users.

To clear an alert

1 2 3

In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click More and then select Clear from the drop-down list.

To assign an alert to an individual

1 2 3

In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click Assign. You can assign an alert to a user for their action or information.

4 5

Select a user to whom you want to assign the alert. Click OK.

To change the policy that is associated with an alert

1 2

In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. The Alert Policy Wizard is also used to create a policy.

Click More and then select Edit Policy from the drop-down list.

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 Viewing the details for a single alert on page 486. See Viewing the details of the alert policy associated with an alert on page 487. See Filtering by alert type on page 487.

About using the Summary View for monitoring NetBackup alerts

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

Viewing alerts by severity

You can drill down to see details for alert categories.

492

Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails

To view alerts by severity

1 2 3

In the OpsCenter console, select Monitor > Alerts. Select Summary View from the drop-down list. The drop-down list is located at the top-right corner of the page. In the Alert Summary by Severity section, do either of the following:

Click the number of alerts (link) for a particular alert severity from the table. For example, click the number that is shown for Critical alerts. Or Click a colored section of the pie chart that corresponds to a particular alert severity. For example, click the red section of the pie chart to view details for critical alerts.

See About using the Summary View for monitoring NetBackup alerts on page 491.

Monitoring Audit Trails

You can manage and monitor audit trails using the OpsCenter features.

About Audit Trails

Audit trails is a record of all the user initiated activities. An audit trail consists of the changes that are made in the NetBackup environment. For example, changes such as creating a policy, deactivating a policy, or modifying a policy. The audit trails feature in OpsCenter lets you enable audit trail logging for NetBackup. Note: OpsCenter monitors, reports , and manages audit trails for the NetBackup master servers for the version 7.1 or later. You can control the audit settings and generate an Audit Trails Report. Through OpsCenter, you can set the audit logs retention period and also enable or disable audit trail logging. Audit trails display the following information in the form of columns:

Category: Displays the changes that are made to policies, storage units, jobs, audit configuration, audit service, pool, and storage server. For example, when a storage unit is added, modified, or deleted. Action: Displays the action performed, such as whether a policy is modified, a storage unit is created, or a storage server is deleted.

Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails

493

Description: Gives a brief information about the category and the action performed. It also gives the identity of the category. User: Gives the information about the user who initiated the action. Timestamp: Displays the time when the action was performed. Master Server: Displays the name of the master server on which the action is performed. Reason: Displays the reason for the change that is made, if given by the user who makes the change. By default, the column is hidden. Details: Displays the old and new values of the attributes that are modified. Some of the attributes that are modified are Clients, Hardware, Operating System (OS), and Policy Generation.

About the Audit Trails report

The Audit Trails report is a high-level summary report that is added to the reports tree. This report displays the number of changes that are made in the NetBackup environment. The report is displayed in the form of a chart. You can view the report in a Distribution chart or Historical chart format The chart displays the count of audit records for each category. Some of the categories are Policy, Audit Configuration, Job, Audit service, Storage unit, Pool, and Storage Server. You can hover the mouse on each colored section of the chart to know the count and the percent changes for each category. You can drill down the report by clicking any colored section of the chart. You can view the count of changes for each action for the selected category. For example, if you click the Policy section, the chart displays the total audit count for policies created, policies modified, and policies deleted. To view the details of the audit trails report in a tabular form, click the link Show Chart as Table. The table displays information about the Audit Category, Total Audit Count, and Percentage. The table also displays the information about Audit Action when you drill down the chart.

About OpsCenter features for Audit Trails

OpsCenter helps you to configure audit logging and generate the Audit report. Through OpsCenter, you can:

Manage the audit settings of the NetBackup master server. Monitor audit trails. Generate alerts if audit service goes down.

494

Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails

Configure audit trail retention period in OpsCenter.

Use the various features of OpsCenter and generate the Audit report. You can enable or disable the audit settings, and set the retention period of the logs. You can set OpsCenter to generate alerts when the NetBackup Audit manager services are turned on or off. You can also set the retention period for the audit logs.

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. See Managing Audit Trails settings on page 535.

Monitoring Audit Trails

OpsCenter helps you to monitor the audit trails. To monitor them, select Monitor > Audit Trails. 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. See Using filters to customize your views on page 74. To create a custom filter to view audit trail data

1 2 3

Select the Create Filter icon. The Edit Audit filter dialog box is displayed. Enter a name for the filter in the Name field. Select the column name that you want to filter from the drop-down list. The options available are Category, Action, User Name, Domain Name, Domain Type, Time Stamp, Object Name, and Master Server. Object Name is filtered based on the entity names present in the description. From the Operator drop-down list, select the operator =. Use != if you do not want to match a specific value. In the Value text box, enter or select a value. If you select Time Stamp as the column, a calendar icon appears for value. Click the calendar icon to choose the required date and click OK.

Select And or Or from the drop-down list to build the filter query.

Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails

495

5 6

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

496

Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails

Chapter

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, you can view and manage your NetBackup environment, which also includes OpsCenter alert policies, storage, and devices. Note that OpsCenter or OpsCenter Analytics can only monitor and manage NetBackup. It cannot monitor or manage other products like Symantec NetBackup PureDisk, Symantec Enterprise Vault etc. The OpsCenter server collects data from NetBackup master servers, stores it in a database, and displays it on demand. Most of the data is sent by NetBackup and appears almost instantaneously after it changes. (Network, system delays, or browser refresh settings can affect how quickly it appears). This data is collected

498

Managing NetBackup using Symantec OpsCenter Controlling the scope of Manage views

mainly using notifications. For most operations and changes in NetBackup, NBSL sends a notification to OpsCenter. See How OpsCenter collects data from NetBackup on page 364.

Controlling the scope of Manage views

The content that is shown in the Manage views is based on your current View pane selection. You can select the following default option from the View pane:
ALL MASTER SERVERS Select ALL MASTER SERVERS to view information for all the NetBackup servers in your environment.

In addition to using the default view i.e. ALL MASTER SERVERS, you can also create your own views from Settings > Views or by using Java View Builder. For example, you can create a view like Geography to view details about master servers in a particular region like Europe. More information about how to create views using Settings > Views is available. See About OpsCenter views on page 409. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. Use the following procedure to view details of all master servers or specific master servers. To view details of all master servers

In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane.

To view details of specific master servers

1 2

In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane. Deselect the checkbox next to ALL MASTER SERVERS and select specific master servers from the list of master servers. Ensure that other master servers are unchecked. Click Apply Selection.

Managing 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. Table 8-1 Topic
See About OpsCenter alert policies on page 499. See Viewing the details for a single alert policy on page 500. See Filtering on type of alert policy on page 500. See About creating (or changing) an alert policy on page 501.

Topic contents and description Description

Explains the concept of alert policies.

Explains how to view the details for an alert policy. Explains how to filter and view the alert policies that are of interest to you. Explains how to create an alert policy using the Alert Policy Wizard.

See Managing an alert policy on page 517. Explains the tasks that are available for managing a single alert policy. Management includes tasks like editing, copying, deleting, activating, or deactivating an alert policy. See Viewing the alerts associated with an alert policy on page 518. Explains how you can view the alerts that are associated with an alert policy.

About OpsCenter alert policies

OpsCenter provides tools to create and manage alert policies and handle any resulting alerts that the policies generate. Alert policies help you manage your NetBackup environment by providing constant monitoring of your NetBackup systems. When certain events or conditions occur in your environment, OpsCenter helps you manage your NetBackup server network by generating alerts or sending email and trap notifications (or both). When a NetBackup system event triggers an alert (based on your alert policies), the following occurs:

OpsCenter sends email or SNMP notices to any recipients that are configured in the policy. The OpsCenter console displays views to help you track and manage these alerts.

You can specify email or SNMP notification in response to an alert, which lets administrators focus on other job responsibilities. Administrators do not need to monitor a terminal continuously.

500

Managing NetBackup using Symantec OpsCenter About managing alert policies

Alert policies are defined as informational, warning, major, or critical. Under certain circumstances there may be issues among multiple OpsCenter users. For instance, an OpsCenter user changes a policy while another user tries to remove the same policy.

Viewing the details for a single alert policy

All the details that are associated with an alert policy can be viewed from the bottom of the Manage > Alert Policies view under the General tab. The General tab displays all the details that are shown in the table. To view the details for a single alert policy

1 2

In the OpsCenter console, select Manage > Alert Policies. Click a drill-down link from the Name column. The alert policy details are shown at the bottom of this view under the General tab.

Filtering on type of alert policy

A filter is available in the Manage > Alert Policies view to limit the types of alert policies that appear. You can filter using any of the following three built-in filters. These filters are available from the drop-down list which is present on top of the table.
All Alert Policies Enabled Alert Policies Select this filter to view all alert policies. Select this filter to view the alert policies that are enabled. Select this filter to view the alert policies that are disabled.

Disabled Alert Policies

You can also create your own filters which let you focus on only the specific alert policies that interest you. See Using filters to customize your views on page 74. To filter on type of alert policy

1 2

In the OpsCenter console, select Manage > Alert Policies. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

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 create policies to automate responses to key events in your enterprise. For example, you can create a policy to alert you when a job fails on a specific master server. You can monitor for frozen media and email the operator when the number of frozen media exceeds a threshold value. You can then take corrective action. OpsCenter periodically retrieves data from NetBackup based on notifications and a wait time (of up to 15 minutes). This time delay between the NetBackup Activity Monitor and the OpsCenter console can mean that many intermediate job states may be lost. The following topics provide more information about alerts. See OpsCenter Alert conditions on page 501. See Additional information on job policy change condition on page 508. See Adding an alert policy on page 509. See About understanding alert counts in the Monitor view on page 516.

OpsCenter Alert conditions

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

Periodic alert conditions

Table 8-2 lists the alert conditions, alert category, and descriptions.

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

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

Alert condition

Job finalized

Events-based

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, of the specified policy or client ended in the specified status.

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. Events-based An alert is generated when any of the selected media is frozen.

Media

Frozen media

Suspended media Events-based An alert is generated when any of the selected media is suspended. Exceeded max media mounts Media required for restore Events-based An alert is generated when a media exceeds the threshold number of mounts. Events-based An alert is generated when a restore operation requires media. The restore operation may require a specific media which contains the specific image to be restored. Periodic An alert is generated when the number of available media becomes less than the predefined threshold value. An alert is generated when the percentage of suspended media exceeds the predefined threshold value. An alert is generated when the percentage of frozen media exceeds the predefined threshold value.

Low available media

High suspended media

Periodic

High frozen media

Periodic

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, you can specify the threshold value for a particular policy in percentage, bytes, kilobytes (KB), megabytes (MB), gigabytes (GB), terabytes (TB) or petabytes (PB) and generate alerts. The generated alert can also show available catalog space using these units. An alert is generated when catalog backup does not take place for a predefined time period. This does not necessarily mean that if you do not receive this alert, the catalog backup was successful.

Alert condition

Catalog Catalog Space low Periodic

Catalog not Backed up

Periodic

Catalog Backup Disabled

Periodic

An alert is generated when all the catalog backup policies are disabled. If the policy has been defined for a server group, an alert is generated for every master server within the group that satisfies this criteria. The alert is not generated if no catalog backup policy exists for a master server.

Tape

Mount Request

Events-based An alert is generated on a media mount request. An alert is generated when no cleaning tapes are left.

No Cleaning Tape Periodic

Zero Cleaning Left

Events-based An alert is generated when a cleaning tape has zero cleaning left.

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 policy based on Disk Pool Full condition generates an alert only when the used capacity of the disk pool reaches the high water mark. Events-based An alert is generated when the selected disk volume(s) is down. An alert is generated when a disk volume capacity is running below the threshold limit.

Disk Volume Down

Low Disk Volume Periodic Capacity Drive is Down

Events-based An alert is generated when a drive in a specified robot or media server in the selected server context goes down. An alert is generated when the percentage of down drives exceeds the predefined threshold value.

High Down Drives Periodic

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. By default, this alert is automatically cleared when the communication is re-established.

Master Server Unreachable

Events-based An alert is generated when OpsCenter loses contact with the master server. This alert condition means that the connection between OpsCenter and the managed NetBackup master server is lost. It does not necessarily mean that NetBackup backups are not working.

Lost Contact with Events-based An alert is generated when OpsCenter loses Media Server contact with the media server. Service Stopped Events-based An alert is generated when the selected service stops on any of the selected servers in the selected view. Events-based An alert is generated when the Symantec ThreatCon level is equal to or more than the threshold level that you specify. To create the alert policy, select the Symantec ThreatCon alert condition and then specify the threshold ThreatCon rating. The Symantec ThreatCon alerts are cleared automatically when the ThreatCon level becomes less than the threshold level that you have specified. For example, if you have created an alert policy that alerts you when the Symantec ThreatCon level becomes 3, then the alert is cleared automatically once the ThreatCon level becomes 2 or less. Job Policy Change Events-based

Symantec ThreatCon

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. 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 select a particular job policy, only the selected job policy is monitored for change. If you do not select any job policy, all the job policies are monitored for changes.

Alert condition

Additional information on job policy change condition

Review the following text for job policy alert condition. Only the following policy attributes are monitored for job policies:
Policy name Checkpoint interval Effective date Compression Block level incrementals Snapshot method Master server Collect bmr info Fail on error Frozen image Number of copies Residence Schedules Storage unit Policy client type 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

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. The required information and the required number of screens vary depending on the alert condition you choose. For some alert conditions, you can skip the optional screens. Note: The Alert Policy Wizard is also used when you edit an alert policy. To add an alert policy

1 2

In the OpsCenter console, select Manage > Alert Policies. Click Add. The Alert Policy Wizard appears. See Alert Policy Wizard on page 511.

Enter a Name, Description, and Alert Condition on the General panel. See OpsCenter Alert conditions on page 501. Click Next to continue. You may click Cancel to exit the wizard at any stage.

510

Managing NetBackup using Symantec OpsCenter About managing alert policies

On the Alert Condition Properties panel, specify attributes for the alert condition that you selected. The attributes differ for each alert condition. For many alert conditions (for example, for the Job Finalized condition), you may need to enter threshold attributes and other required or optional attributes. These attributes define and limit the alert. Click Next.

On the Scope panel, select the view that should be verified for the alert condition. You can select a view and a node that contains a group of master servers and also specific objects. You may also select only specific objects of a particular view or node to be checked for the alert condition. To select a specific master server, first deselect the view or node that contains the master server and then select the master server. You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. See Alert Policy Wizard on page 511. Note that you can also view and select additional attributes like policies, clients, media servers etc. on expanding the views and nodes from this page (wherever applicable). These attributes are located under the applicable views or nodes for specific alert conditions. Note: This page is not shown if you have selected the Symantec ThreatCon alert condition. This is because the Symantec ThreatCon alert condition does not depend on any views or master servers. You must select at least one object, node, or view from this page. Click Next to continue.

Optionally, on the Actions panel, in the Email Recipients and Trap Recipients sections, you can select email or SNMP recipients (or both) to receive the alert notification. See Adding email recipients on page 515. See Adding SNMP trap recipients on page 516. Note that if you create an alert policy and do not define any recipients, the alert is still displayed in the Monitor > Alerts view. In the Severity section, do the following:

Select a severity level from the Alert Severity drop-down list. (If this alert occurs, the alert is displayed in the Monitor > Alerts view.)

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. With Severity of email/trap sent for cleared alert option, you can configure the severity for an email or trap that is sent when an alert is cleared. The default severity level is Informational. The Activate Condition option is checked by default. By default, the policy will be active once you create it. Deselect the Activate Condition option if you want to deactivate the policy. You can always activate or deactivate the policy later from the OpsCenter console. See Managing an alert policy on page 517.

7 8

Click Save to save the alert policy. Click Finish once the policy is successfully created.

Alert Policy Wizard

The Alert Policy Wizard consists of four panels. Table 8-3 Setting
Name

Alert Policy Wizard General Panel Description

Enter a name for the alert policy. The name must be unique. This is a required field.

Description Alert Condition

Enter a description for the alert policy. Select an alert condition from the list of alert conditions that are available. See OpsCenter Alert conditions on page 501.

Table 8-4 Setting

Alert Policy Wizard Alert Condition Properties Panel Description

Specify attributes for the alert condition that you selected. The attributes differ for each alert condition. For many alert conditions (for example, for the Job Finalized condition), you may need to enter threshold attributes and other required or optional attributes. These attributes define and limit the alert.

Specify properties for the selected alert condition

512

Managing NetBackup using Symantec OpsCenter About managing alert policies

Table 8-5 Setting

View

Alert Policy Wizard Scope Panel Description

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

514

Managing NetBackup using Symantec OpsCenter About managing alert policies

Table 8-5 Setting

Alert Policy Wizard Scope Panel (continued) Description

Finalized alert condition, you can select the view as well as the specific policies and clients that should be checked for the alert. You can view the applicable attributes like policy name, client name, media server name, robot number, drive IDs etc. for the following alert conditions:

Job Finalized Drive is Down Media Required for Restore Service Stopped Frozen Media Suspended Media Exceeded Max Media Mounts Disk Group Full Disk Volume Down Job Policy Changed Hung Job

Note: This page is not shown if you have selected the

Symantec ThreatCon alert condition. This is because the Symantec ThreatCon alert condition does not depend on any views or master servers. You must select at least one object, node, or view from this page.

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. Select a severity level from the Alert Severity drop-down list. (If this alert occurs, the alert is displayed in the Monitor > Alerts view.)

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. With Severity of email/trap sent for cleared alert option, you can configure the severity for an email or trap that is sent when an alert is cleared. The default severity level is Informational. In OpsCenter, an alert is raised with the severity specified in the alert policy. Whenever this alert is cleared, an email or trap informing the user that the alert is cleared is sent with the same severity that is defined in the alert policy. This is the default behavior. For example, you may have created an alert policy for a Hung Job alert condition with a Critical severity. As a result, you receive Hung Job alert with Critical severity. When this Hung Job alert gets cleared, you receive an email or trap that informs you that the alert has been cleared. This email or trap also has a Critical severity. You can now configure the severity for this email or trap from Critical to some other severity like Informational while creating the alert policy. Note that you can configure the severity only for email or trap.

Severity of email/trap sent for cleared alert

Activate the Policy

The Activate Condition option is checked by default. By default, the policy will be active once you create it. Deselect the Activate Condition option if you want to deactivate the policy. You can always activate or deactivate the policy later from the OpsCenter console. See Managing an alert policy on page 517.

See Adding an alert policy on page 509.

Adding email recipients

Follow this procedure to add email recipients to an Alert Policy. To add email recipients

1 2

While creating an alert policy using the Alert Policy Wizard, go to the Actions screen. On the Actions screen, click To, Cc, or Bcc from the Email Recipients section.

516

Managing NetBackup using Symantec OpsCenter About managing alert policies

In the Add Email Recipients dialog box, select the specific recipients from the Recipient Name column and click To, Cc, or Bcc based on your requirements. Click OK.

Adding SNMP trap recipients

Follow this procedure to add SNMP trap recipients to an Alert Policy. To add SNMP trap recipients

1 2 3 4

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

Add Trap Recipients dialog box

In the Add Trap Recipients dialog box, select the specific recipients from the Recipient Name column and click To.

About understanding alert counts in the Monitor view

Alerts apply only to the object (master server) where the corresponding alert policy is created. When alerts are raised for that policy they are raised on the selected object. For example, a Frozen Media alert occurs when any of the selected media on the selected master server (object) are frozen. Consider a case where you create an alert policy for a selected view that contains two master servers. For creating the policy, you select an alert condition of type of Frozen Media. Since this master server is present in the view, the alert is listed when you select the specific server as well as the specific view from the View Pane. But some types of alerts, for example High Job Failure Rate apply across groups. In this case, jobs from all of the master servers in the selected group are used to calculate the job failure rate. The alert does not apply to a single master server in the group but applies to the server group on which the alert policy was created. This means that only one alert is raised for the group if the job failure rate for the servers in the selected group is more than a user-defined threshold. An alert is not generated for every master server that is a part of the group. Therefore, the alert is listed only when you select the server group on which alert policy is created (or a parent group of that group).

Managing NetBackup using Symantec OpsCenter About managing alert policies

517

If you create this type of alert policy for a single managed server, the alert is raised on the server since the server is the selected object. The alert can also be viewed if all the nodes or views that contain the master server are selected. The following OpsCenter alert policy conditions apply across groups:

High Down Drives High Frozen Media High Job Failure Rate High Suspended Media Low Disk Volume Capacity Low Available Media

Managing an alert policy

Use the following procedure to edit, delete, copy, activate, or deactivate an alert policy. You can copy and use an alert policy on another managed master server. The copy of the alert policy is available in the alert policy details table where you can make changes to it. To edit an alert policy

1 2 3

In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click Edit. The Alert Policy Wizard is used to create or edit a policy. When you edit an alert policy, the alert condition specific to the policy is selected by default in the Alert Policy Wizard. You cannot select a different alert condition while editing an alert policy. See Adding an alert policy on page 509.

To delete an alert policy

1 2 3

In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click Delete.

To copy an alert policy

1 2 3

In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click More and then click Copy from the drop-down list.

518

Managing NetBackup using Symantec OpsCenter About managing NetBackup storage

4 5

In the Copy Alert Policy dialog box, enter the new name for the alert policy. Click OK. The copy of the alert policy is available in the alert policy details table where you can make changes to it.

To enable or disable an alert policy

1 2 3

In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click More and then click Enable or Disable from the drop-down list.

Viewing the alerts associated with an alert policy

Use the following procedure to view the alerts that are associated with an alert policy. To view the alerts associated with an alert policy

1 2 3

In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click More and then select View Alerts from the drop-down list.

About managing NetBackup storage

This view is displayed when you select Manage > Storage. Included in this view are subtabs for Storage Unit, Storage Unit Group, and Storage Lifecycle Policy. Using these subtabs you can view detailed information about NetBackup storage for the current View pane selection. See Controlling the scope of Manage views on page 498. 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. using the Manage > Storage > Storage Unit view. See Manage > Storage > Storage Unit Group Explains the capabilities that are available view on page 521. using the Manage > Storage > Storage Unit Group view.

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.

See Manage > Storage > Storage Lifecycle Policy view on page 522.

Manage > Storage > Storage Unit view

This view is displayed when you select Manage > Storage > Storage Unit. This view shows the details for a storage unit for the current View pane selection. There is one row in the table for each storage unit for the current selection in the View pane. See Controlling the scope of Manage views on page 498. 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. Click the link to view details about the storage unit. This column specifies the type of robot (if any) that the storage unit contains. This column specifies a unique, logical identification number for the robotic library. This column lists the density of the storage unit. This column specifies whether the storage unit is available exclusively on demand. This happens only when a policy or schedule is explicitly configured to use this storage unit. . This column specifies the absolute path to a file system or a volume available for disk backups.

Robot Type

Robot Number

Density On Demand

Path

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:

Storage Unit Type Capacity Free Space

520

Managing NetBackup using Symantec OpsCenter About managing NetBackup storage

High Water Mark Max. Concurrent Jobs Staging Low Water Mark Can Exist On Root NDMP Host Enable Block Sharing Transfer Throttle Master Server Last Seen Time Host Fragment Size Multiplexing Disk Type Time Last Selected Disk Pool Host List

See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 71. 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.

Viewing the details for a single storage unit

Use the following procedure to view the details for a single storage unit.

Managing NetBackup using Symantec OpsCenter About managing NetBackup storage

521

To view details for a single storage unit

1 2

In the OpsCenter console, select Manage > Storage > Storage Unit. Click a storage unit name (drilldown link) from the Name column in the table. The storage unit details are shown at the bottom of this view under the General tab. This tab displays many of the available columns of the table.

Manage > Storage > Storage Unit Group view

This view is displayed when you select Manage > Storage > Storage Unit Group. This view shows the details for a storage unit group for the current View pane selection. The table contains one row for each storage unit group for the current selection in the View pane. See Controlling the scope of Manage views on page 498. 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. Click the link to view details about the storage unit group. This column specifies the order that storage units are selected when they are included in a group. . This column specifies the date and time when the storage unit group was last seen.

Storage Unit Selection

Last Seen Time

The following task can be performed from this view:

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

Viewing the details for a single storage unit group

Use the following procedure to view the details for a storage unit group. The storage unit group details are shown at the bottom of this view under the following tabs:

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. This tab shows the details of the storage units that are a part of the storage unit group.

Storage Unit

To view details for a single storage unit group

1 2

In the OpsCenter console, select Manage > Storage > Storage Unit Group. Click the name of a storage unit group (drilldown link) from the Name column in the table.

Manage > Storage > Storage Lifecycle Policy view

This view is displayed when you select Manage > Storage > Storage Lifecycle Policy. This view shows the storage lifecycle policy details for the current View pane selection. A storage lifecycle consists of one or more storage units. The table contains one row for each Storage lifecycle policy for the current selection in the View pane. See Controlling the scope of Manage views on page 498. 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. Click the link to view details about the storage lifecycle Policy. This column lists the data classification that has been selected for the storage lifecycle, which applies to all of the storage units in the lifecycle. For example, the data might be classified as gold or silver. This column specifies the priority that a policy has for backup resources. The default for all policies is 0, the lowest priority possible. Any policy with a priority greater than zero has priority over the default setting. . This column lists the master server that is associated with the storage lifecycle Policy. Click the link to view more details about the master server.

Data Classification

Job Priority

Master Server

The following tasks can be performed from this view:

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

Viewing the details for a single storage lifecycle policy

Use the following procedure to view the details for a single storage lifecycle Policy. The details are shown at the bottom of this view under the following tabs:
General This tab shows the details of the storage unit group that are also shown in the table. This tab shows the details of the storage destinations that are a part of the storage lifecycle policy.

Storage Destinations

To view the details for a storage lifecycle policy

1 2

In the OpsCenter console, select Manage > Storage > Storage Lifecycle Policy. Click the name of a storage lifecycle policy (drilldown link) from the Name column in the table.

Viewing the details for a master server associated with a storage lifecycle policy
Use the following procedure to view the details for a master server that is associated with a storage lifecycle policy. The details are shown on a separate page. To view the details for a master server associated with a storage lifecycle Policy

1 2

In the OpsCenter console, select Manage > Storage > Storage Lifecycle Policy. Click the name of the master server (drilldown link) from the Master Server column in the table.

About managing NetBackup devices

Under certain circumstances there may be issues among multiple OpsCenter users managing devices. For instance, a user brings a drive down while another user tries to bring up the same drive. Table 8-11 lists the topics on how to manage NetBackup devices.

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. Explains the capabilities that are available using the Manage > Devices > Robot view. Explains the capabilities that are available using the Manage > Devices > Disk Pool view. Explains the capabilities that are available using the Manage > Devices > SAN Client view. Explains the capabilities that are available using the Manage > Devices > FT Server view.

See Manage > Devices > Drive view on page 524. See Manage > Devices > Robot view on page 528. See Manage > Devices > Disk Pool view on page 530.

See Manage > Devices > SAN Client view on page 532.

See Manage > Devices > FT Server view on page 533.

Manage > Devices > Drive view

This view is displayed when you select Manage > Devices > Drive. This view shows details for the drives that are configured for use by NetBackup for the current View pane selection. This view shows information about all the drives and also includes disabled or unreachable drives. See Controlling the scope of Manage views on page 498. 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. Click the link to view details about the drive. This column lists the name of the device host (media server) where this drive is attached. If multiple drive paths are configured, this column contains Multiple. If the drive is configured as a shared drive (SSO), this column contains Multiple. This column lists the name of the master server that is associated with the drive.

Device Host

Master Server

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. Example: hcart2, hcart3, 4MM.

Robot Type

This column specifies the type of robot that contains this drive. Example: TL4, TLD.

Enabled

This column contains Yes if the path is enabled. The column contains No if the path is not enabled. If multiple drive paths are configured, this column contains Multiple.

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:

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

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71. 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. See Viewing the details for a master server associated with a drive on page 527. See Filtering on NetBackup drive category on page 527.

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. To view the details for a single drive

1 2

In the OpsCenter console, select Manage > Devices > Drive. Click the name of the drive (drilldown link) from the Drive Name column in the table. Detailed properties and status for the drive are shown at the bottom of the view under the General tab. The Paths tab shows the paths that were configured for the drive.

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. To view the details for a master server

1 2

In the OpsCenter console, select Manage > Devices > Drive. Click the name of the drive (drilldown link) from the Master Server column in the table. Details for the specific master server are shown on a separate page.

Filtering on NetBackup drive category

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

Up Drives

Down Drives

Mixed Drives

In addition to using the built-in filters, you can also create your own custom filters. See Using filters to customize your views on page 74. To filter details by type of drive

1 2

In the OpsCenter console, select Manage > Devices > Drive. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.

528

Managing NetBackup using Symantec OpsCenter About managing NetBackup devices

Manage > Devices > Robot view

This view is displayed when you select Manage > Devices > Robot. This view shows details for the robots that are configured for use by NetBackup for the current View pane selection. See Controlling the scope of Manage views on page 498. 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. The robot name contains the type and number of the robot, for example TLD(3). Click the link to view details about the robot.

Device Host

This column lists the name of the device host where this robot is attached. This column contains the robot serial number. If the robot is controlled by a remote host, this column contains the name of the host that controls the robot. This column lists the master server that is associated with the robot. Click the link to view details about the master server.

Serial Number Robot Control Host

Master Server

Media Server

This column lists the media server that is associated with the robot. Click the link to view details about the media server.

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:

Robot Type Robot Number Inquiry Information Last Seen Time Max Drive Max Slot Remote ID

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71. 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. See Viewing the details for a master server associated with a robot on page 529. See Viewing the details for a media server associated with a robot on page 530.

View the details for a master server that is associated with a robot View the details for a media server that is associated with a robot

Viewing the details for a single robot

Use the following procedure to view the details of a single robot. To view the details for a single robot

1 2

In the OpsCenter console, select Manage > Devices > Robot. Click the name of the robot (drilldown link) from the Robot Name column in the table. Detailed properties for the robot are shown at the bottom of the view under the General tab. The Paths tab shows the paths that were configured for the robot.

Viewing the details for a master server associated with a robot

Use the following procedure to view the details of a master server that is associated with a robot. To view the details for a master server associated with a robot

1 2

In the OpsCenter console, select Manage > Devices > Robot. Click the name of the master server (drilldown link) from the Master Server column in the table. Detailed properties for the master server are shown on a separate page.

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. To view the details for a media server associated with a robot

1 2

In the OpsCenter console, select Manage > Devices > Robot. Click the name of the media server (drilldown link) from the Media Server column in the table. Detailed properties for the media server are shown on a separate page.

Manage > Devices > Disk Pool view

This view is displayed when you select Manage > Devices > Disk Pool. This view shows details for the disk pools that are configured for use by NetBackup in the current View pane selection. See Controlling the scope of Manage views on page 498. 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. For OpenStorage, the server type depends on the vendor name. This column lists the number of disk volumes in the disk pool. This column lists the amount of storage space in use. This column lists the total raw, unformatted size of the storage in the disk pool. This column lists the estimated amount of disk space available for storage after file metadata overhead is taken into account. This column lists the low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit.

Number of Volumes

Used Capacity Raw Size

Usable Size

Low Watermark (%)

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. More information about how to customize tables and view specific columns is available. See About using tables on page 71. 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.

Viewing the details for a disk pool

Use the following procedure to view the details for a disk pool. The details for the disk pool are shown at the bottom of the Manage > Devices > Disk Pool view under the following tabs:
General This tab shows the detailed properties for a disk pool. Click the master server link to view details about the master server that is associated with the disk pool. This tab shows details about the disk volumes that are associated with the disk pool. This tab shows details about the storage servers that are associated with the disk pool.

Disk Volume

Storage Server

To view the details for a disk pool

1 2

In the OpsCenter console, select Manage > Devices > Disk Pool. Click the name of the disk pool (drilldown link) from the Name column in the table. The details are shown at the bottom of this view.

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. This view shows details for the SAN clients that are configured for use by NetBackup in the current View pane selection. See Controlling the scope of Manage views on page 498. 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. This column lists the state of the FT device on the SAN client. The different states can be active, disabled etc.

Usage Preference No. of FT Media Servers

This column determines when to use the FT media server. This column lists the number of NetBackup media servers that support FT transport and that the client can send data to or receive data from. The number of minutes to wait for an FT media server for a backup operation. The number of minutes to wait for an FT media server for a restore operation. This column lists the master server that is associated with the SAN client.

Backup Wait Period

Restore Wait Period

Master Server

The Version column does not appear, but can be added to your view by clicking the Table Settings icon. The following task can be performed from this view:
View the details of a SAN client See Viewing the details for a SAN client on page 533. See Viewing the details for a master server associated with a SAN client on page 533.

View the details of a master server that is associated with a 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. The details for the SAN Client are shown at the bottom of Manage > Devices > SAN Client view under the following tabs:
General This tab shows detailed properties and status for the SAN client. Click the master server link to view details about the master server that is associated with the SAN client. This tab shows the FT target devices information for the selected SAN client.

FT device

To view the details for a SAN client

1 2

In the OpsCenter console, select Manage > Devices > SAN Client. Click the name of the SAN client (drilldown link) from the Name column in the table. The details are shown at the bottom of this view.

Viewing the details for a master server associated with a SAN client
Use the following procedure to view the details of a master server that is associated with a SAN client. To view the details for a master server associated with a SAN client

1 2

In the OpsCenter console, select Manage > Devices > SAN Client. Click the name of the master server (drilldown link) from the Master Server column in the table. Detailed properties for the master server are shown on a separate page.

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. See Controlling the scope of Manage views on page 498. The table that appears in this view shows the following columns by default:

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. Click the link to view details about the robot.

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. This column specifies the number of FT connections to allow to a media server.

Max Allowed Connections

The following tasks can be performed from this view:

View the details of an FT server See Viewing the details for an FT server on page 534. See Viewing the details for a master server associated with an FT server on page 535.

View the details for a master server that is associated with an FT server

Viewing the details for an FT server

Use the following procedure to view the details for an FT server. The details for the FT server are shown at the bottom of Manage > Devices > FT Server view under the following tabs:
General This tab shows detailed properties and status for the FT server. This tab shows the FT target devices information for the selected FT server.

FT device

To view the details for an FT server

1 2

In the OpsCenter console, select Manage > Devices > FT Server. Click the name of the Fibre Transport server (drilldown link) from the Name column in the table. The details are shown at the bottom of this view.

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. To view the details for a master server associated with an FT server

1 2

In the OpsCenter console, select Manage > Devices > FT Server. Click the name of the master server (drilldown link) from the Master Server column in the table. Detailed properties for the master server are shown on a separate page.

About managing NetBackup Hosts

This view is displayed when you select Manage>Hosts. This view displays detailed information for OpsCenter audit reports. for the current Master server selection.

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. To enable the Audit trail logging

1 2 3

Log on to OpsCenter server host with administrator privileges. Click Manage and click Hosts. From the Master Server tab, select the required master server and click Edit Audit Settings. Select the Enable audit trail logging with NetBackup Environment check box to enable the audit logging process. Note: If audit logging is initiated in NetBackup, the Enable audit trail logging with NetBackup Environment check box appears as selected. You can disable audit logging by clearing this check box.

Under Retention period, select the Always retain all audit trail logs option to retain the logs forever. To retain logs for a specific period of time, enter the value in the Retain audit logs for days text box. By default, the retention period is set to 90 days. Click Save to save the settings.

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. This view gives detailed information about the OpsCenter Capacity Licensing report for all or selected master servers.

About Capacity License report

A Capacity Licensing report gives a summary of the amount of data that is protected. The report is classified by the options Enterprise Disk, PureDisk, and RealTime. The report gives capacity totals for each client, thus making it easier to verify capacity totals for each client. The report displays totals on the basis of the number of policies and subtotals for each capacity tier. A log file is also created, which gives information about how the totals are calculated. The report is generated in the form of an Excel sheet. The report contains information about capacity totals backed up for each client. The report displays details such as number of policies per client and their name and the total kilobytes backed up. 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. You can thus ensure that the data that is backed up is within the permitted license amount. The report displays the amount of data with the licensed amount for the Capacity Totals for Enterprise Disk, PureDisk, and RealTime.

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. The data can either be on the clients or the devices where the software is installed. The data can also be on the software that is used to provide the backup functionality.

Determining the capacity licensing

The bpimagelist command is used to obtain image and fragment information for all backups for the past 30 days. The NetBackup Deployment Analyzer examines the image headers in the NetBackup catalog to determine the amount of data that NetBackup protects. The data is measured in terabytes. The final total is the sum of terabytes for each client and policy combination that the analyzer examines. The Deployment Analyzer calculates the total data that needs to be protected. The analyzer uses the size of the last full backup for the last 30 days. A day is defined as the 24 hour period from midnight to midnight. The analyzer sums all backups that started within that period. For some policy types, 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.

Generating a Capacity Licensing report

The Capacity Licensing report is generated in the form of an Excel sheet. This report can be emailed or exported in the XLS format to the required email address or location. To generate the Capacity Licensing report

To generate the Capacity Licensing report it is mandatory to enable License Deployment data collection and to configure an agent. The Settings tab helps you to enable them. Select Settings > Configuration > NetBackup. Select the required master server and click Edit. The Edit Master Server page is displayed.

538

Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis

Select the Configure agent link to configure an agent. Select the Enable License Deployment Data Collection check box as shown in the following figure.

Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis

539

In the OpsCenter console, click Manage > Deployment Analysis. The Capacity Licensing page is displayed as shown in the following figure.

The Capacity Licensing page contains details about the previously created report, log file, and data collection. You can view the previously generated report with the available link under the Last Successful Report Date header. A log file is generated when the Capacity License report is generated. You can view the log file with the View Log link. See About the Capacity Licensing page on page 541.

Click New Report to generate a new report. The Create Capacity Licensing Report page is displayed.

540

Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis

Select the Collect data and run report on all Master Servers option to generate a report for all the master servers. Select the Collect data and run report on specific Master Servers option to generate a report for only the required master servers. Select the required master servers from the list, the following image displays both the options.

7 8

Click Next. The Report Options page is displayed. Enter the recipients email address in the To and CC fields. The Subject field displays the default text Capacity Licensing Report, you can change the subject line if required. Enter a message in the Message field.

Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis

541

10 To export the report to the required location, select the Export report (XLS
format) check box. You can change the export location path from the Settings > Configuration > Report Export Location tab. See Setting report export location in OpsCenter on page 318.

11 Select Run Report to initiate the data collection. A message to show that
report generation has started is flashed.

When report generation is complete, you can open the .xls file or save the file for later viewing. 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.

About the Capacity Licensing page

The Capacity Licensing page contains information about the Capacity License report and the data collection status. The report section contains details about the report in the form of a table. The headers are:

Last Successful Report Date: Displays a link to the previously generated report. The link itself contains information about the date and time of the last successful report. Status: Displays the report status as the name suggests. The status shows as Failed when the report is not generated. Exceptions: Displays the reasons for the report generation failure. An example exception detail message can be- Data collection failed for selected master servers. If the report generation is successful, this column shows a blank. Last Successful Report Log: Displays a link to the log file that is generated when the report is generated. The log file is very useful in analyzing the Capacity Licensing report. If the report generation fails, this column shows a blank.

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. The headers are:

Master Server: Displays the list of master servers for which the report is generated. If you select the Collect data and run report on specific Master Serversoption, then the columnn displays only those master servers that you select. Data Collection Status: Displays the status of data collection. Last Licensing Data Collection Date: Displays the date and time when the last licensing data is collected. The column shows a blank when data collection fails. Exceptions: Displays the reason for data collection failure. An example is OpsCenter Agent is not connected. Prerequisites Status: Displays a link when the prerequisites have not been completed. Click the link to know the details about the prerequisites that need to be completed. Prerequisites can be, an agent not configured, or data status collection is not enabled for a master server.

Final location of the reports and logs

The reports and log files are located at the following locations:

The final report is located at - SERVER_INSTALL_DIR/fsdb/fetb/report. The log file is located at - SERVER_INSTALL_DIR/fsdb/fetb/log. The last successful backup report is located at SERVER_INSTALL_DIR/fsdb/fetb/backup. The output of bpimagelist for each server is located at SERVER_INSTALL_DIR/fsdb/fetb/data.

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. When the master server is not enabled or when the agents are not configured, the report is not generated and shows errors. Another cause of errors whena report is not generated is the network connectivity issue. Make sure that the you have network connectivity. Table 8-17 describes the possible Capacity License report issues and their solution. 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.

Capacity License report issues, causes, and solution Solution

If the agent is down OpsCenter will try to automatically connect to the agent after every 10 minutes. 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. You can also initialize the agent explicitly by first disabling the master server and then enabling it.

Failed to initialize agent Agent is not connected or there could be a network issue.

Server side exception unknown oid

Confirm that the agent is connected. If the agent is disconnected, wait for 10 minutes This error is displayed when the agent gets for it to reconnect. You can also initialize the disconnected while data collection is in agent explicitly by first disabling the master progress. server and then enabling it. Retries exceeded cannot connect on opscenter_agent Connection to the Agent service is lost Confirm that the agent is connected. If the agent is disconnected, wait for 10 minutes for it to reconnect. You can also initialize the agent explicitly by first disabling the master server and then enabling it. Confirm that the master server is connected.

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.

If the agent is down OpsCenter will try to automatically connect to the agent after every 10 minutes. You can also initialize the agent explicitly by first disabling the master server and then enabling it.

544

Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis

Chapter

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.

546

Guided Recovery Setting up for cloning

OpsCenter retrieves information for you such as databases and control files, shortening the Oracle clone setup time. A validation process increases the rate of successfully completing the cloning operation. You do not need access to the original database to perform the cloning operation.

Setting up for cloning

Oracle uses metadata cataloging, which enables database information to display in OpsCenter. Metadata cataloging must occur during the backup from the Oracle database to be cloned. The collected metadata displays within the OpsCenter interface to guide the clone operation to enable metadata collection on the client host. Do the following before you perform a Guided Recovery cloning operation:

On UNIX and Linux systems, ensure that the Oracle metadata parameter in the client's bp.conf is set at backup time as follows:
ORACLE_METADATA=YES

Or, use the SEND command to set the metadata parameter:

SEND ORACLE_METADATA=YES

On Windows systems, first place the following text into a text file (for example, new_config.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.txt bpsetconfig is located in the install_path\NetBackup\bin\admincmd

directory.

Set up all destination file paths before you run the cloning operation, because the operation does not create new file paths during the process. Ensure that the user has write access to these paths.

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. Examples are Solaris 9 to Solaris 10 and Oracle 11 to Oracle 11. The cloning operation does not support offline tablespaces or raw tablespaces. The cloning operation does not support Oracle Automatic Storage Management (ASM). To use a different user or a different group for the clone, you must change what the permissions of the backup image are to be at backup time. Add the 'BKUP_IMAGE_PERM=ANY' to the send commands during the backup of the source database. If the destination client is different than the source client, perform an alternate restore procedure. On Windows systems, if the NetBackup client service runs as the Oracle user, then that user needs to be granted the right to "Replace a process level token". On Oracle 9 for Windows, run the Oracle service under the Oracle user account. By default, it runs under the local system. On Oracle 10G systems and later, you can run under the local system. On Windows systems, if you are cloning to the same system, shut down the source database to successfully complete the operation. Otherwise, an error indicating the database cannot be mounted in exclusive mode appears. On UNIX and Linux systems, if the cloning user shares an existing Oracle home, the user must have write access to some directories such as DBS.

Performing a cloning operation

You need to log onto OpsCenter, to perform a cloning operation. OpsCenter is the Web GUI that you use to perform all guided recovery operations. To perform a cloning operation on an Oracle database in OpsCenter

1 2

When you log onto OpsCenter, the first screen that appears is the Monitor Overview screen. Along the top of the screen, click Manage > Oracle Cloning. On the Select Master Server screen, use the drop-down menu to select the master server that you want to work with, then click Go. See Select Master Server screen on page 549.

548

Guided Recovery Performing a cloning operation

The Select Source Database screen lets you filter the list of databases by database name, host name, database version, platform, and date. The default condition is to display all databases that are backed up in the default date range. Click Show Databases. More information is available on this screen. See Select Source Database screen on page 549.

The databases appear under the filtering part of the same screen. Select the database on which you want to perform a cloning operation by clicking option at the left side of the desired database entry. Then click Next>. The Select Control File Backup screen shows a timeline view of the control file backups. Select the icon for the desired control file backup from the timeline view. You can hover over the icon to display the control file details. If the icon represents multiple backups, you can hover over the icon to display all versions of the backup for that time periods. Additional information is available to verify that you have selected the correct control file. The lower left corner of the screen lists three links. More information is available about these links. See Select Control File Backup screen on page 549. Click on the icon of the control file backup you want to restore for the clone of the selected database. The default is the latest backup selected. Then click Next>.

The Destination Host and Login screen contains parameters for the destination of the clone to be created. Enter the destination host name in the text box that is provided or click Browse and select from a list of available hosts. Note the following prerequisites concerning the destination host:

The platform type of the source and destination must be the same. A NetBackup client must be installed. A compatible version of Oracle must be installed.

See Destination host and login screen on page 550. For operating system authentication, enter a user name, password (Windows), and domain (Windows). Then click Next>.

The Define Destination Parameters screen appears. The five tabs on this screen are used to change database attributes, the destination paths of control files, data files, and redo logs, and restore options. After you have changed the destination parameters, click Next>. See Destination Parameters screen on page 551.

Guided Recovery Select Master Server screen

549

The SelectionSummary screen lets you scan the information you have entered on the previous screens. Links to the recovery sets and destination database attributes let you view and verify any changes you have made. When you are satisfied with the summary information, click Next>. See Selection summary screen on page 552.

The Pre-clone Check screen lets you validate the database attributes and the file paths. To validate, click the underlined word here. If a directory path does not already exist, the validation check flags the error. If a file already exists, the validation check also flags the error, so that the cloning operation does not overwrite the file. See Pre-clone check screen on page 552. When you are ready to launch the cloning operation, click Launch Cloning Process. A display appears that is similar to the NetBackup Activity Monitor.

Select Master Server screen

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

Select Source Database screen

When the Select Source Database screen first appears, the lowest portion of the screen shows a list of the latest backups for all the databases that the master server knows about for the default date range. The upper portion of the screen shows parameters for filtering the list of databases. If the list is long, you can filter what databases appear by database name, host name, database version, and date range. Multiple filter parameters can be used at the same time. For example, to show only the Solaris databases that are backed up between 11/05/2009 and 11/12/2009, select Solaris from the Platform: pulldown menu. Then select the dates from the calendar icons. Then click Show Databases to display the new filtered list of databases.

Select Control File Backup screen

The Select Control File Backup screen is a timeline view of all the control files that are backed up for the selected database. The timeline displays an icon for each control file that is associated with the backed up database. When you first enter this screen, the latest backup control file is already selected .

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, type of media, the size of the backup, etc. Multiple control files may be displayed on the timeline. To view all the instances of control files, you may need to increase the scope of the timeline. You can display the timeline in days, weeks, months, or years. If multiple control files were backed up during a single timeline unit, a different icon appears representing more than one control file (for example, if the database was backed up twice in an hour). To select from among these files, hover over the icon. A popup lists each control file in table format. It shows several items including the backup name and the type of media. Click option next to the desired control file. You can also click one of the links in the lower left of the screen to verify that you have selected the proper control file.

View Database Schema shows the schema of the selected control file. It shows how the database is laid out by listing each data file name, tablespace name, and its size. View Datafiles Recovery Set shows the data file backups to be used for the restore process. It also shows the backup and image information that is displayed for each data file. The data file recovery set is generated only for the files that are backed up as part of an incremental strategy. Even though files that are backed up as part of a full backup do not appear in this list, the clone still completes successfully. If the image spans media, only the first media is shown in the list. View Archived Log Recovery Set shows the archive log backups that may be used to recover the database to the latest point in time of that control file. This set is generated only for the files that are backed up as part of an incremental strategy. Even though files that are backed up as part of a full backup do not appear in this list, the clone still completes successfully.

Destination host and login screen

The Select Destination Parameters screen lets you enter the destination host and the Oracle logon information. For Windows, you are asked for the domain name, user name, and password. For UNIX and Linux, you are asked only for the user name. The following rules apply to the selection of the destination host:

The destination must be of the same platform type as the source of the clone. A NetBackup client must be installed. A compatible version of Oracle must be installed.

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. You can modify these values if not appropriate for the destination database. Note: The Windows information you enter on this screen is case sensitive. Be sure to enter the Windows information appropriately. The Destination Parameters screen contains the following tabs:

Database Attributes. This pane appears when you first enter the Database Attributes screen. Each attribute name has identical source and destination attributes. You can change the destination attribute of the instance name, database name, and database home. Note that the instance name is case sensitive while the database name is not case sensitive. On Windows, For the temporary tablespace/datafile, if the datafile(s) is/are being put back to the same location do not modify the path or if you do modify it...make sure it is identical to the source path including case (upper, lower, mixed). Control File Paths. This pane displays the source path and the destination path for each control file. You can change a control file destination path by clicking in the associated text window and entering the new path. You can also click Browse to navigate to the desired path. When you change a path, a highlight bar appears around the text window as a visual indicator that this path has changed. Data File Paths. This pane lets you change the destination path for one or more data files. Enter the path in the text window provided, then select the data files on which to apply it, and press the Apply option. Redo Log Paths. This pane displays the source path and the destination path for all redo logs. You can type in a new destination path or click Browse to navigate to the desired path. When you change a path, a highlight bar appears around the text window as a visual indicator that this path has changed. Restore Options. This pane displays restore options. The option that is displayed on this pane is Number of parallel streams for restore and recover.

When you are done making changes on this screen, click Next>. All the information from the previous screen is saved in preparation for the cloning operation. All the changes that are made in this screen are temporary and are active only for the cloning session.

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 date and time of the selected control file backup, and the backup media type. The database recovery set and the archived log recovery set. The destination database attributes selected in the previous screen and the database initialization parameters to be used for the cloning operation.

Pre-clone check screen

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

Job Details screen

The Job Details screen is intended to reflect the NetBackup Activity Monitor. More information is available on the Activity Monitor. See the NetBackup Administrator's Guide, Volume I.

Post-clone operations
Perform the following after the cloning operation has completed:

On UNIX and Linux systems, update the oratab file with the appropriate instance information. On UNIX and Linux systems, if the cloning operation fails, do the following cleanup:

If the database is active, shut down the database. Remove init<SID>.ora, spfile<SID>.ora, and any other files associated with the SID being used, from the <$ORACLE_HOME>/DBS directory.

Guided Recovery Troubleshooting Guided Recovery

553

Remove all data files.

On Windows systems, if the cloning operation fails, use the dbca utility to delete the database. dbca sometimes removes directories, so verify before retrying the operation. If a cloned Oracle database contains read-only tablespaces or datafiles, you must make them read-write before RMAN backs them up, or RMAN cannot restore them. After the backup (cloning operation), you can return the items to read-only. The following shows an example of the sequence of steps in the process:

Back up Oracle database A which contains read-only tablespace TABLE1. Clone database A to database B. Use the Oracle alter tablespace command to make tablespace TABLE1 read-write. You may revert to read-only if you want. Back up database B. Use RMAN to restore database B.

Troubleshooting Guided Recovery

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

Troubleshooting files for metadata collection operations at the time of the backup
From the Oracle client host:

netbackup/logs/bphdb legacy logs netbackup/logs/dbclient legacy logs (The directory must be writable by the Oracle users.) ncf unified logs, OID 309, New Client Framework ncforautil unified logs, OID 360, New Client Framework Oracle Utility ncforaclepi, OID 348, New Client Framework Oracle Plugin

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 362, NetBackup Agent Request Service dars unified logs, OID 363, 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 309, New Client Framework ncfnbcs unified logs, OID 366, New Client Framework NetBackup Client Services

From the NetBackup master server:

netbackup/logs/vnetd legacy logs nbars unified logs, OID 362, NetBackup Agent Request Service dars unified logs, OID 363, Database Agent Request Service

From the NetBackup master server:

netbackup/logs/bprd legacy logs nbars unified logs, OID 362, NetBackup Agent Request Service dars unified logs, OID 363, Database Agent Request Service

From the Symantec OpsCenter server:

<SYMCOpsCenterServer>/config/log.conf file opscenterserver unified logs, OID 148 (The default location is <SYMCOpsCenterServer >/logs) opscentergui unified log, OID 147 (The default location is <SYMCOpsCenterGUI>/logs)

Troubleshooting files for Guided Recovery cloning operations

From the Oracle client host:

netbackup/logs/bphdb legacy logs (Includes the obk_stdout and obk_stderr logs.) netbackup/logs/bpdbsbora legacy logs

Guided Recovery Troubleshooting Guided Recovery

555

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

From the NetBackup master server:

netbackup/logs/vnetd legacy logs netbackup/logs/bprd legacy logs nbars unified logs, OID 362, NetBackup Agent Request Service dars unified logs, OID 363, Database Agent Request Service

From the Symantec OpsCenter server:

<SYMCOpsCenterServer>/config/log.conf file opscenterserver unified logs, OID 148 (The default location is <SYMCOpsCenterServer >/logs) opscentergui unified log, OID 147 (The default location is <SYMCOpsCenterGUI>/logs)

556

Guided Recovery Troubleshooting Guided Recovery

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.50/7.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. See About SNMP versions on page 558. See SNMP versions supported in OpsCenter on page 559. See About the Management Information Base (MIB) and OpsCenter support on page 559. See Configuring the SNMP trap community name for OpsCenter on page 574. See Configuring the SNMP version for sending SNMP traps on page 575. See Alert configuration settings in OpsCenter on page 576. See Frequently asked SNMP and OpsCenter questions on page 577.

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. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. SNMP enables network administrators to manage network performance, find and solve network problems, and plan for network growth. SNMP is based on the manager model and agent model. This model consists of a manager, an agent, a database of management information, managed objects, and the network protocol. The manager provides the interface between the human network manager and the management system. The agent provides the interface between the manager and the physical devices being managed. The manager and agent use a Management Information Base (MIB) and a relatively small set of commands to exchange information. The MIB is organized in a tree structure with individual variables, such as point status or description, being represented as leaves on the branches. A numeric tag or object identifier (OID) is used to distinguish each variable uniquely in the MIB and in SNMP messages.

About SNMP versions

Many versions of SNMP are available. The versions of SNMP protocol are as follows:

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

The original SNMPv2 (SNMPv2p) Community-based SNMPv2 (SNMPv2c) User-based SNMPv2 (SNMPv2u) SNMPv2 star (SNMPv2*).

SNMPv3

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, and support for proxies. The security is based on that found in SNMPv2u and SNMPv2*. RFC 1905, RFC 1906, RFC 2261, RFC 2262, RFC 2263, RFC 2264, and RFC 2265 define this protocol.

SNMP versions supported in OpsCenter

OpsCenter supports the following SNMP versions:

SNMPv1 SNMPv2c SNMPv3

About the Management Information Base (MIB) and OpsCenter support

Each SNMP element manages specific objects with each object having specific characteristics. Each object and characteristic has a unique object identifier (OID) that is associated with it. Each OID consists of the numbers that are separated by decimal points (for example, 1.3.6.1.4.1.2682.1). These OIDs form a tree. The MIB associates each OID with a readable label and various other parameters that are related to the object. The MIB then serves as a data dictionary that is used to assemble and interpret SNMP messages. See SNMP traps on page 559. See Alert descriptions in OpsCenter on page 562.

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

560

Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter

Table 10-1 Name

1.3.6.1.2.1.1.3.0

OpsCenter trap binding Value

This field is the time (in hundredths of a second) between when OpsCenter server service starts and the OpsCenter trap is sent. See Request for Comment (RFC) 1905 and 2576 for a detailed definition. http://www.ietf.org/rfc/rfc1905.txt http://www.ietf.org/rfc/rfc2576.txt Example: 1173792454

1.3.6.1.6.3.1.1.4.1.0

This field is the unique identifier for this trap. See RFC 1905 and RFC 2576 for a detailed definition. http://www.ietf.org/rfc/rfc1905.txt http://www.ietf.org/rfc/rfc2576.txt Example: 1.3.6.1.4.1.1302.3.12.10.2.0.4

1.3.6.1.4.1.1302.3.12.10.1.1

This field is the alert recipient name.

(iso.org.dod.internet.private.enterprises.p Example: Nancy Nieters roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.alertRecipients) 1.3.6.1.4.1.1302.3.12.10.1.2 This value specifies the alert ID, alert status, and alert summary in the (iso.org.dod.internet.private.enterprises.p following format: roducts.veritascc.ccTrapDefinitionsBranc Alert ID (Alert Status) Alert Summary h.ccTrapVarsBranch.alertSummary) Example: 100 (Active) Job Completed with Exit Status 0 1.3.6.1.4.1.1302.3.12.10.1.3 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.alertDescription) This field is the alert description. Examples for each alert condition are available. See Alert descriptions in OpsCenter on page 562.

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.

1.3.6.1.4.1.1302.3.12.10.1.4 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.policyName) 1.3.6.1.4.1.1302.3.12.10.1.5 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.objectType) 1.3.6.1.4.1.1302.3.12.10.1.6 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.collectorNam e) 1.3.6.1.4.1.1302.3.12.10.1.7

This field is blank and not used.

This field is blank and not used.

(iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition Example: 10.212.12.148 sBranch.ccTrapVarsBranch.ccHost) 1.3.6.1.4.1.1302.3.12.10.1.8 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.sourceId) 1.3.6.1.4.1.1302.3.12.10.1.9 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.ccObject) 1.3.6.1.4.1.1302.3.12.10.1.10 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.sampleData)

This field is the IP address of the OpsCenter server.

This field is blank and not used.

This field is blank and not used.

This field is blank and not used.

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.

1.3.6.1.4.1.1302.3.12.10.1.11

(iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition Example: Informational sBranch.ccTrapVarsBranch.ccAlertSeveri ty) 1.3.6.1.4.1.1302.3.12.10.1.12

(iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition Example: 13-10-2008 06:57:34 00 sBranch.ccTrapVarsBranch.ccAlertTime)

This field shows the time when the alert gets cleared.

The first two OIDs listed in the table are standard SNMP OIDs. The other OIDs starting from 1.3.6.1.4.1.1302.3.12.10.1.1 to 1.3.6.1.4.1.1302.3.12.10.1.12 are OpsCenter OIDs. As per SNMPv2c trap definition, the two standard SNMP OIDs must be present as part of every trap. All the 12 OpsCenter OIDs are defined in the OpsCenter MIB files. However, the two standard OIDs are not defined in the OpsCenter MIB files.

Alert descriptions in OpsCenter

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

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 5:00 PM Tree Type : Policy Nodes : Root Node % Failed Jobs: 100.0 Alert Policy: high job failure rate policy view OpsCenter Server: ccs-sol-qe-17 Severity: Warning

Hung job

Alert Raised on: September 7, 2009 2:21 PM Job: 25888 Tree Type : 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

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

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

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, 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, 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.0 Alert Policy: high percentage suspended media OpsCenter Server: localhost Severity: Warning High frozen media

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

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, 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 9:54 AM Tree Type : Server Nodes : ccs-sol-qe-13 Threshold: 10 Minute(s) Last Catalog BackUp Time: September 6, 2009 5:21 PM Alert Policy: Catalog not Backed up OpsCenter Server: ccs-sol-qe-17 Severity: Warning Catalog Backup Disabled Alert Raised on: September 5, 2009 3:44 PM Tree Type : Server Nodes : ccs-win-qe-1 Alert Policy: Catalog Backup Disabled OpsCenter Server: ccs-sol-qe-17 Severity: Warning

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: - Volume Group: 000_00000_TLD Request Time: February 4, 1991 12:56 AM Alert Policy: Mount Request OpsCenter Server: ccs-sol-qe-12 Severity: Warning

No Cleaning Tape

Alert Raised on: August 17, 2009 12:30 PM 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

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

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

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, 2009 10:39 AM Tree Type : Server Nodes : ccs-win-qe-1 Media server : omlinux2 Drive Name: BNCHMARK.VS640.000 Drive Number: 1 Robot Number: 0 Alert Policy: drive down-individual alert Device Path: /dev/nst0 OpsCenter Server: localhost Severity: Critical High Down Drives Alert Raised on: August 12, 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

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

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, 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, the SNMP trap community name is OpsCenter (by default). Symantec OpsCenter uses a public community named OpsCenter. Public community implies a read-only access to SNMP traps. Use the following procedures to configure the SNMP trap community name on Windows and UNIX. To configure the SNMP trap community name for OpsCenter traps on Windows

On the OpsCenter server host, stop all the OpsCenter server services.
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the nm.conf file. The file shows the following entry:
nm.trapCommunity=OpsCenter

Modify the value of nm.trapCommunity from OpsCenter to some other name.

3 4

Save the nm.conf file after making the changes. Restart all OpsCenter services.
INSTALL_PATH\OpsCenter\server\bin\opsadmin.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

On the OpsCenter server host, stop all the OpsCenter services.

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

Navigate to /opt/SYMCOpsCenterServer/config directory and open the nm.conf file. The file shows the following entry:
nm.trapCommunity=OpsCenter

Modify the value of nm.trapCommunity from OpsCenter to some other name.

3 4

Save the nm.conf file after making the changes. Restart all OpsCenter services.
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Configuring the SNMP version for sending SNMP traps

The default SNMP version through which SNMP traps are sent in OpsCenter is SNMPv2c. However, this SNMP version can be changed by modifying a configuration file. The following procedure explains how to configure the default SNMP version on Windows and UNIX. To configure the SNMP version for sending SNMP traps on Windows

On the OpsCenter server host, stop all the OpsCenter services.

INSTALL_PATH\server\bin\opsadmin.bat stop

Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the nm.conf file. The file shows the following entry:
nm.trapVersion=v2c

Modify the value of nm.trapVersion from v2c to v1 (for SNMPv1) or v3 (for SNMPv3).

3 4

Save the nm.conf file after making the changes. Restart all OpsCenter services:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

576

Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter

To configure the SNMP version for sending SNMP traps on UNIX

On the OpsCenter server host, stop all the OpsCenter services:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

Navigate to the OpsCenter configuration directory:

cd /opt/SYMCOpsCenterServer/config

Open the nm.conf file. The file shows the following entry: nm.trapVersion="v2c" Modify the value of nm.trapVersion from v2c to v1 (for SNMPv1) or v3 (for SNMPv3).

4 5

Save the nm.conf file after making the changes. Restart all OpsCenter services:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

Alert configuration settings in OpsCenter

In OpsCenter, you can customize a few alert settings using the am.conf configuration file. The am.conf configuration file is located at the following default location:
Windows UNIX <INSTALL_DIR>\OpsCenter\server\config\am.conf <INSTALL_DIR>/SYMCOpsCenterServer/config/am.conf

The alert configuration settings are described as follows: Note: By default all alert configuration parameters are set to true.
am.autoClear Set this parameter to true, if you want to automatically clear the alerts. Make sure that the am.autoClear parameter is set to true, to apply the change in the am.notifyOnAutoClear parameter setting. Set this parameter to true, if you want to send notification after an alert was automatically cleared.

am.notifyOnAutoClear

Understanding and configuring OpsCenter alerts About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007

577

am.notifyOnManualClear

Set this parameter to true, if you want to send notifications after manually clearing alerts.

Note: If you set an alert configuration parameter to a value other than true or false, OpsCenter assumes it as false.

Frequently asked SNMP and OpsCenter questions

Question Answer

What are the default versions of SNMP that SNMPv1, SNMPv2c, and SNMPv3. are supported in OpsCenter? What is SNMPv2c? How it is different from See About SNMP versions on page 558. SNMPv2? Is the OpsCenter SNMP community name configurable? Yes. See Configuring the SNMP trap community name for OpsCenter on page 574.

How is the OpsCenter community related to The "OpsCenter" community used by the public community? OpsCenter is public, but the community name is maintained as "OpsCenter". Is the default community name of "OpsCenter" just a name for the community, Generally, the "default read community but still considered public because of certain string" for the public community is "public". attributes? Public community means read-only access to SNMP traps.

About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007
Microsoft System Center Operations Manager 2007 (SCOM), formerly Microsoft Operations Manager (MOM), is a next-generation performance and event-monitoring product from Microsoft. Microsoft System Center Operations Manager Management Pack for NetBackup lets you monitor and manage NetBackup alerts using Microsoft System Center Operations Manager 2007 (SCOM 2007). By detecting and alerting you on critical conditions, this Management Pack helps prevent possible service outages. The SCOM Management Pack for NetBackup and the documentation is available for download on the Symantec Support Web site.

578

Understanding and configuring OpsCenter alerts About managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows

http://www.symantec.com/docs/TECH139344

About managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows
You can monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.50 or 7.51 on Windows. By detecting and alerting you on critical conditions, HP OpenView Network Node Manager (NNM) can help you to prevent possible service outages. You can download and use the nom_trapd.conf file to monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.50 or 7.51. By using nom_trapd.conf file and configuring NNM and OpsCenter, NNM can receive the SNMP traps that have been configured in OpsCenter. As a result, NNM can be used for the centralized management of NetBackup alerts. Note: The term HP OpenView Network Node Manager (NNM) in this section refers specifically to HP OpenView Network Node Manager 7.50 or 7.51.
nom_trapd.conf file and the documentation is available for download on the

support site. http://entsupport.symantec.com/docs/295154 More information about OpsCenter alerts is available. See OpsCenter Alert conditions on page 501.

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. By using OpsCenter, you can track the effectiveness of data backup and archive operations by generating comprehensive business-level reports.

580

Reporting in OpsCenter About OpsCenter reports

OpsCenter 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 benefit from the reporting and the management capabilities of OpsCenter. The audiences include IT (Information Technology) managers, application owners, IT finance teams, external compliance auditors, legal teams, line-of-business managers, external customers, IT architects, and capacity planning teams.

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

Reporting in OpsCenter About OpsCenter reports

581

Manage Folders tab

Use this tab to manage folders where you have saved your reports. See About managing reports folders in OpsCenter on page 599.

Report creation wizards in OpsCenter

OpsCenter provides wizards, which guide you through the entire report creation procedure. To create a report, in the OpsCenter console on the Reports tab, click Create New Report. The following report creation options are available on the Select Report Creation Option panel:

Create a report using an existing Report Template . See Creating an OpsCenter report using a Report Template on page 585. Create a custom report. See Creating a custom report in OpsCenter on page 591. Create a report using SQL Query. See Creating an OpsCenter report using SQL query on page 592.

Reports > Report Templates

This section provides details of the Report Templates that are available in OpsCenter. OpsCenter provides a number of Report Templates (or standard or canned reports) that you can modify and generate a new report of that kind. In the OpsCenter console, when you click the Reports tab, the Report Templates home page is displayed. Click any of the Report Templates to view the respective report with default parameter values. See About Report Templates descriptions on page 612. Figure 11-1 shows various components of a report that is generated using a template.

582

Reporting in OpsCenter About OpsCenter reports

Figure 11-1
Manage reports toolbar Time filters Report Templates tree Report views Report area

Report Template

Tabular view

Report Templates tree

This tree lists all Report Templates that are available in OpsCenter. Use this toolbar to save, export, or email the generated report. Use these time filters to view the data for a specific period of time. OpsCenter reports are displayed here. Reports can be viewed in different forms or views, Distribution, Historical, or Ranking. Use these options to change the current report view.

Manage report toolbar

Time filters

Report area Report views

About custom reports in OpsCenter

Apart from generating reports using the existing templates, you can also create custom reports in OpsCenter by changing the report parameters as required. See Creating a custom report in OpsCenter on page 591.

About custom SQL query in OpsCenter

In OpsCenter, you can create reports by directly running SQL queries. Using this report creation option, you do not need to go through multiple parameter selections.

Reporting in OpsCenter Report Templates in OpsCenter

583

Note: You can create only tabular reports by running SQL queries. You can also run stored procedures using this feature. See Creating an OpsCenter report using SQL query on page 592.

Report Templates in OpsCenter

Symantec OpsCenter provides a set of Report Templates or standard or canned reports that have parameters set to default values. You can modify the default parameters and generate reports to view the required data. OpsCenter reports help you to have a good visibility into your data protection environment. See Reports > Report Templates on page 581. Report Templates are categorized as follows:
Enterprise Vault Archiving Reports These reports are generated based on the archive data that is collected from Enterprise Vault. You can report on the number of messages that are archived across mailboxes or on the size of these messages before and after the archive operation. The backup reports show the information that is related to backups, such as success rate, job status, and protected bytes. This category also includes recovery reports.

Backup Reports

Note: If you select Reports > Activity

Planning > Job Size in the OpsCenter user interface, the report that appears displays the wrong client name. Instead of showing the client names, a list of backed up VM images is displayed in this report. In addition, the list of VM images may not be accurate. Catalog Reports These reports provide details about the catalogs.

584

Reporting in OpsCenter Report Templates in OpsCenter

Chargeback Reports

The chargeback reports provide details of the backup services expenditures. Using these reports you can track the backup and the recovery usage and the associated cost. You can calculate the cost of data protection management and chargeback to customers and business units.

Client Reports

These reports provide details about clients such as backup status, restore job details, or summary dashboard. Disk-based data protection (DBDP) reports show disk pool capacity and its usage, performance of clients on LAN or SAN, NetBackup Storage Lifecycle Map These reports provide media data, such as tape count or usage These reports provide details of throughputs These reports show all details about the backup job policies in NetBackup. These reports provide details about restore operation.

Disk & Tape Device Activity Reports

Media Reports

Performance Reports Policy Reports

Restore Reports

About report filters in OpsCenter

There can be hundreds of records or thousands of MB of the data that you may not be concerned about. For example, you want to view only those jobs that were successful. To view this specific data, you need to use the status filter. By setting this filter to Successful while generating the Job Count report, you can view all jobs that were successful. OpsCenter provides a number of filters that you can use to view the required data. For each report category there is a different set of filters. In OpsCenter 7.1, 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 specific reports. This filter has been added in the custom reports and the following Client reports:

Recovery Point Objective Client Risk Analysis

Reporting in OpsCenter Report Templates in OpsCenter

585

These Client reports can be accessed from the Reports > Report Templates page by selecting Client Reports > Risk Analysis folder. Also note the following point about Schedule/Level Type filter. On applying Schedule/Level Type filter with value All, the following reports consider only Full and Incremental schedule type jobs:

Advanced Success Rate All Failed Backups Consecutive Failures Report Success Rate Line

The Backup Media Role filter when applied to the Tapes Expiring In Future and Tapes Expiring Now reports does not return any data as data is miscalculated in OpsCenter.

Creating an OpsCenter report using a Report Template

This section provides the procedure to create a report using an existing Report Template . To create a report using an existing Report Template

1 2

In the OpsCenter console, click Reports. On the Reports Template tab, click Create New Report. To view a report output of a template, select a template in the reports tree. The report output is as per the default parameter values. You cannot modify any of the report parameters. By clicking the Create New Report option, you can launch the report creation wizard that guides you through the entire report creation procedure. Here you can modify the report parameters and view the required data.

3 4

In the Report Wizard, retain the default selection Create a report using an existing Report Template and click Next. On the Report Templates list, expand a report category to see the Report Templates within it. Select the Report Template that you want to create a report from and click Next. Select time frame and other filters as required and click Next. Modify display options and click Next.

5 6

586

Reporting in OpsCenter About managing reports in OpsCenter

About managing reports in OpsCenter

This section provides information on the operations that you can carry out on the standard reports that you generate in OpsCenter. You can carry out the following operations:

Saving a report See Saving an OpsCenter report on page 588. Exporting a report See Exporting an OpsCenter report on page 588. Emailing a report See Emailing a report in OpsCenter on page 589.

Save report and email report dialog boxes

A description of the Save report and Email report dialog box options follows in the table. Table 11-1 Option
Report name

Save report dialog box options Description

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

The report name must be unique across the report tree.

The report name must not contain any special characters like (/ \ * ? | ") The report name must not be more than 220 characters. Description Enter the short description for the report.

Reporting in OpsCenter About managing reports in OpsCenter

587

Table 11-1 Option

Folder

Save report dialog box options (continued) Description

Select Public or Private folder. If you save the report in a public folder, all other OpsCenter users can view it. If you save the report in a private folder, only you can view it. Expand the Public or Private folder and select a folder where you want to save the report. Depending on the folder type that you have selected - public or private - the folders displayed for selection vary.

Create New

Click this option to create a new public or private folder. Clicking this option changes the view of Folder. Enter the folder name and click OK. This folder is made available in the Folder tree for selection. Select this newly created folder where you want to save the report.

Overwrite if report already Select this check box if you want to overwrite the existing exists in the selected folder report with the same name in the same folder. If you do not select this check box and save a report with a name identical to any of the existing reports in the selected folder, a confirmation message is displayed before you overwrite the existing report.

Table 11-2 Option

Select Format

Email report dialog box options Description

Select one of the following formats:

PDF HTML CSV TSV XML

Select Content

Select one of the following report formats:

Distribution Historical Ranking

Email

Enter appropriate email details like address, subject, and message.

588

Reporting in OpsCenter About managing reports in OpsCenter

Saving an OpsCenter report

You can save a standard report. This action saves the filters that you have selected while generating a report. You can use this set of filters to regenerate the reports with the current time selections. These reports are saved in the OpsCenter database, which you can view using the My Reports tab. Note that in OpsCenter 7.1, you cannot save a report whose name contains any special characters like (/ \ * ? | "). Also when you upgrade from VBR, NOM, OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1, older reports with these special characters are replaced with '_' (underscore). See About managing My Reports on page 593. To save a report

1 2 3 4

In the OpsCenter console, click Reports > Report Templates. From the Reports tree, select the report template that you want to save. In the right-hand report view area, click the Save As Report icon. The Save Report pop-up screen opens. On the Save Report screen, enter the required details. See Save report and email report dialog boxes on page 586.

Click OK. After a successful save, My Reports tab is displayed with this report selected. Note: You cannot save a report name that contains special characters like (/ \ * ? | ")

Exporting an OpsCenter report

Using OpsCenter, you can preserve report data in files or print the data. See File formats available in OpsCenter on page 589. You can open the exported file using other applications, such as a spreadsheet program or a text editor. To export a report

1 2

In the OpsCenter console, click Reports > Report Templates. From the Reports tree, select the report template that you want to export.

Reporting in OpsCenter About managing reports in OpsCenter

589

3 4

In the report view area at the right-hand side, click the Export Report icon. The Export Report pop-up screen opens. On the Export Report pop-up screen, select the export options that you want to export the report with: File format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. See Save report and email report dialog boxes on page 586.

Click OK. The system displays the export options pertaining to the file format you have selected. Select those options and export the report.

File formats available in OpsCenter

You can export or email OpsCenter reports in the following file formats:
PDF (Portable Document Format) Can be viewed using a PDF reader, such as Adobe Reader

CSV (comma-separated Use with spreadsheet programs, such as MS Excel. values) TSV (tab-separated values) HTML (hypertext markup language ) XML (Extensible Markup Language) Compatible with word-processing applications and text editors

Can be opened using with Web browsers

Can be imported (using user-written scripts) by other programs like databases or billing applications

Emailing a report in OpsCenter

Using OpsCenter, you can email report data to the selected recipients. You can email a report in a number of different file formats. See File formats available in OpsCenter on page 589. To email a report

1 2 3

In the OpsCenter console, click Reports > Report Templates. From the Reports tree, select the report template that you want to email. In the report view area at the right-hand side, click the Email Report icon. The Email Report pop-up screen opens. See Save report and email report dialog boxes on page 586.

590

Reporting in OpsCenter About managing reports in OpsCenter

On the Email Report pop-up screen, select the email options: File format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Enter email IDs in To, Cc, and Bcc text boxes, to which you want to send emails. If these email IDs do not already exist, they are automatically added to the database. Alternatively, you can add existing email recipients. See Adding email recipients to an OpsCenter report mailing on page 590.

6 7 8

Enter the subject of the email. Enter the message that may be a short description regarding the report data that you want to email. Click OK.

Adding email recipients to an OpsCenter report mailing

This section provides information on how to add email recipients to whom you want to send emails. This procedure assumes you've already started the email report procedure. There is more information about this procedure. See Emailing a report in OpsCenter on page 589. To add email recipients

On the Add Email Recipients screen, select the check boxes in front of the email recipients to whom you want to send emails. See Add email recipients dialog box options on page 590. Click To.., Cc.., or Bcc.. depending on where you want to add the selected recipients.

Click OK.

Add email recipients dialog box options

Table 11-3 Option
Recipient Name/Email Address

Add email recipients dialog box options Description

Select the check boxes in front of the email recipients to whom you want to send emails.

Reporting in OpsCenter Creating a custom report in OpsCenter

591

Table 11-3 Option

To.../Cc.../Bcc...

Add email recipients dialog box options (continued) Description

Click To.., Cc.., or Bcc.. depending on where you want to add the selected recipients.

Creating a custom report in OpsCenter

This section provides the procedure to create a custom report. This feature is accessible only to the Symantec OpsCenter Analytics users. This option is disabled in the unlicensed OpsCenter version. To create a custom report

1 2 3 4 5 6

In the OpsCenter console, click Reports. On the Report Templates tab, click Create New Report. On the Report Wizard, select the Create a custom report option and click Next. Select the report category and view type and click Next. Select time frame and other filters as required and click Next. Add conditions as follows:

Select a report column. Select an operator. Select a range of value. Select low threshold and high threshold values. See About OpsCenter report conditions on page 591. Click Add.

When the specified condition is met, a notification is sent to the concerned person.

Click Next.

About OpsCenter report conditions

In the Conditions section of the Custom Report Wizard, specify conditions for notification. Conditions represent potential problems, for example an unusually high percentage of backup job failures or an unusually low quantity of data being backed up. Each exception condition is defined by assigning threshold values for a particular metric, such as Success Rate or Total Backup Job Size. You can set a low threshold, a high threshold, or both. Select a condition while generating a

592

Reporting in OpsCenter Creating an OpsCenter report using SQL query

custom report, so that when a condition is true, an alert is triggered or an email notification is sent. As an example, you can define a backup report with the following conditions:

Success Rate: Low threshold 80% The condition is met whenever the success rate falls below 80 percent. Total Backup Job Size: Low threshold 500 GB, high threshold 1000 GB The condition is met whenever the total size of backed-up data falls outside the range of 500-1000 GB.

Creating an OpsCenter report using SQL query

This section provides the procedure to create a report using SQL query. Only Symantec OpsCenter Analytics users can access the custom SQL query function. Note: OpsCenter Analyst and Reporter do not have access to the custom SQL query option.

Caution: Make sure about the impact that the entered SQL query has on the OpsCenter database before running it. To create a report using SQL query

1 2 3

In the OpsCenter console, click Reports. On the Report Templates tab, click Create New Report. On the Report Wizard, select the Create a report using SQL Query option and click Next.

Reporting in OpsCenter About managing My Reports

593

On the SQL Query page, enter an SQL query to view the required data. For example, to view all NetBackup master servers that monitored and managed by OpsCenter, enter the following SQL query: select * from domain_masterserver

Click Next. You can view all master server details that are stored in the domain_masterserver database table. Note: When you run a stored procedure that has multiple result sets, then output of only the first result set is displayed on the GUI. The output of other result sets is not shown on the GUI.

About managing My Reports

You can save generated reports for your future use. These saved reports are stored in the My Reports tab. Use this section to view the saved reports or modify the parameters of the saved reports and generate new reports out of them. You can also delete the saved reports using the My Reports tab. The following topics provide more information about managing reports. See Creating a report using the My Reports tab on page 593. See Deleting a saved report using the My Reports tab on page 594. See Viewing a saved report using the My Reports tab on page 594. See Editing a saved report using the My Reports tab on page 594. See Exporting a saved report on page 595. See Emailing a saved report on page 595.

Creating a report using the My Reports tab

This section provides the procedure to create a report using My Reports tab.

594

Reporting in OpsCenter About managing My Reports

To create a report using the My Reports tab

1 2

In the OpsCenter console, click Reports > My Reports. On the My Reports tab, click Create New Report. You can create a report in any of the following ways: See Creating an OpsCenter report using a Report Template on page 585. See Creating a custom report in OpsCenter on page 591. See Creating an OpsCenter report using SQL query on page 592.

Deleting a saved report using the My Reports tab

This section provides the procedure to delete a saved report. To delete a saved report

1 2 3 4

In the OpsCenter console, click Reports > My Reports. On the My Reports tab, in the Reports list, expand a report folder to view the reports that are saved within it. Select the check box in front of the report name. Click Delete.

Viewing a saved report using the My Reports tab

You can view the saved reports using the My Reports tab. To view a saved report

1 2

In the OpsCenter console, click Reports > My Reports. On the My Reports tab, in the Reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to view.

Editing a saved report using the My Reports tab

You can edit a saved report. You can edit the report details, such as the report name or the folder where you want to save the edited report. To edit a saved report

1 2

In the OpsCenter console, click Reports > My Reports. On the My Reports tab, in the Reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to edit.

Reporting in OpsCenter About managing My Reports

595

3 4

In the report view area at the right-hand side, click the Save As Report icon. The Save Report pop-up screen opens. On the Save Report screen, enter the required information. See Save report and email report dialog boxes on page 586.

Click OK.

Exporting a saved report

Using OpsCenter, you can preserve saved report data in files or print the data. You can email a report in a number of different file formats. See File formats available in OpsCenter on page 589. You can open the exported file using other applications, such as a spreadsheet program or a text editor. To export a saved report

1 2

In the OpsCenter console, click Reports > My Reports. On the My Reports tab, in the Reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to export. In the report view area at the right-hand side, click the Export Report icon. The Export Report pop-up screen opens. On the Export Report pop-up screen, select the export options that you want to export the report with. Select file format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Click OK. The system displays the export options pertaining to the file format you have selected. Select those options and export the saved report.

3 4

Emailing a saved report

Using OpsCenter, you can email the saved report data to the selected recipients. You can email the report in the following file formats:
PDF (Portable Document Format) Can be viewed using a PDF reader, such as Adobe Reader

CSV (comma-separated Use with spreadsheet programs, such as MS Excel. values) TSV (tab-separated values) Compatible with word-processing applications and text editors

596

Reporting in OpsCenter About managing My Dashboard

HTML (hypertext markup language ) XML (Extensible Markup Language)

Can be opened using with Web browsers

Can be imported (using user-written scripts) by other programs like databases or billing applications

To email a report

1 2

In the OpsCenter console, click Reports > Saved Reports. On the My Reports tab, in the Reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to email. In the report view area at the right-hand side, click the Email Report icon. The Email Report pop-up screen opens. On the Email Report pop-up screen, select the email options: File format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Enter email IDs in To, Cc, and Bcc text boxes, to which you want to send emails. Enter the subject of the email. Enter the message that may be a short description regarding the report data that you want to email. Click OK.

3 4

5 6 7 8

About managing My Dashboard

Your saved reports are preserved in My Reports tab, which you can select and publish on My Dashboard tab. You can select multiple reports and add them in the same dashboard section. Thus, you can create multiple dashboard sections containing a number of reports. You can add only 10 reports in a dashboard. See Adding reports to a dashboard on page 597. See Modifying a dashboard section on page 597. See Deleting a dashboard section on page 598. See Emailing dashboard sections on page 598. See Refreshing My Dashboard on page 599.

Reporting in OpsCenter About managing My Dashboard

597

Reports > My Dashboard options

Select and publish reports on My Dashboard tab. You can select multiple reports and add them in the same dashboard section. Thus, you can create multiple dashboard sections containing a number of reports. You can add only 10 reports in a dashboard. Table 11-4 Option
Add/Edit/Delete

Reports > My Dashboard options Description

You can add multiple Dashboards on this page and one or more reports from My Reports to each of the dashboards. Use Add, Edit, Delete tasks to add, edit, or remove dashboard Select this option if you want to email all the dashboard reports. In the Email Dashboard dialog box that opens, you can specify the format in which you want to email the dashboard reports.along with the other email details. Click OK.

Email Dashboard

Refresh Dashboard

Select this option to update the reports in the dashboard.

Adding reports to a dashboard

This section provides the procedure to add reports to a dashboard. To add reports to a dashboard

1 2 3 4 5 6

In the OpsCenter console, click Reports > My Dashboard. Click Add. On the Add Dashboard Section pop-up screen, enter the section name. Expand the Private or Public Reports folder to view existing reports. Select the check boxes in front of the report names, which you want to publish on the dashboard. Click OK.

Modifying a dashboard section

This section provides the procedure to modify dashboard section.

598

Reporting in OpsCenter About managing My Dashboard

To modify a dashboard

1 2 3 4 5 6 7

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

Deleting a dashboard section

This section provides the procedure to delete a dashboard section. To delete a dashboard section

1 2 3 4

In the OpsCenter console, click Reports > My Dashboard. Click Delete. On the Delete Dashboard Section pop-up screen, select the dashboard section from the drop-down list, that you want to delete. Click OK.

Emailing dashboard sections

You can email your dashboards. To email a dashboard

1 2 3 4

In the OpsCenter console, click Reports > My Dashboard. Click the Email Dashboard icon. On the Email Dashboard pop-up screen, select the format in which you want to send the email. Select email recipients from the To.., Cc.., and Bcc.. as appropriate. Alternatively, enter new email recipients, which are added into the database.

5 6

Enter the email subject and message. Click OK.

Reporting in OpsCenter About managing reports folders in OpsCenter

599

Refreshing My Dashboard
This section provides the procedure to refresh My Dashboard. To refresh My Dashboard

1 2

In the OpsCenter console, click Reports > My Dashboard. Click the Refresh icon.

About managing reports folders in OpsCenter

OpsCenter provides a way to manage folders where you have saved your reports. They can be both private reports and public reports. Using the Manage Folders tab in the Reports section, you can add new report folders, edit names of the existing folders, or delete them. You can also select reports in a particular folder and delete them using this tab. See Adding a reports folder in OpsCenter on page 599. See Editing a reports folder in OpsCenter on page 600. See Deleting reports folders in OpsCenter on page 601. See Deleting reports from a folder in OpsCenter on page 601.

Reports > Manage Folders options

Using the Manage Folders tab in the Reports section, you can add new report folders, edit names of the existing folders, or delete them.

Adding a reports folder in OpsCenter

This section provides a procedure to add a report folder.

600

Reporting in OpsCenter About managing reports folders in OpsCenter

To add a folder

1 2

In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a check box in front of a private folder node or public folder node in which you want to create a new folder.

3 4 5 6

Click Add. In the Create new folder pop-up window, make sure that you have selected only one folder. If multiple folders are selected, the Add option is disabled. Enter the folder name. Click OK. This folder is added in the selected node.

Editing a reports folder in OpsCenter

This section provides a procedure to edit a report folder. To edit a folder

1 2 3 4 5 6

In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a check box in front of a private folder or public folder that you want to edit. Click Edit. In the Edit folder name pop-up window, make sure that you have selected only one folder. If multiple folders are selected, the Edit option is disabled. Edit the folder name. Click OK.

Reporting in OpsCenter Using report schedules in OpsCenter

601

Deleting reports folders in OpsCenter

This section provides a procedure to delete a report folder. If you delete a report folder, all reports that are saved in that folder are deleted. To delete folders

1 2 3

In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a check boxes in front of the private folders or public folders that you want to delete. Click Delete.

Deleting reports from a folder in OpsCenter

This section provides a procedure for deleting the reports that are saved in a public folder or private folder. To delete reports from a folder

1 2

In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a private folder or public folder from which you want to delete the reports. A list of reports that are saved in the selected folder displays at the right-hand side of the page. From the list of reports, select the check boxes in front of the reports that you want to delete. Click Delete.

3 4

Using report schedules in OpsCenter

Using report schedules, you can email or export reports at a scheduled time. Each report schedule is associated with a time schedule at which it emails or sends the specified reports. OpsCenter provides a wizard to create a report schedule. See Creating a report schedule in OpsCenter on page 607. The following table describes the steps that you need to carry out to email or export a report on a specific schedule. See About managing time schedules in OpsCenter on page 610.

602

Reporting in OpsCenter Using report schedules in OpsCenter

Table 11-5

Creating a report schedule

Step Step and reference topic Number

1 Create a time schedule. See Creating a time schedule on page 611. 2 Create a report schedule. OpsCenter provides a wizard to create a report schedule. This wizard lets you specify the following details:

Report schedule name File format in which you want to email or export reports

Select a time schedule. You can either select an existing time schedule that you have created in the first step or create a new schedule from here to associate it with this report schedule. Specify details of export or email options.

Select the reports that you want to export or email on a specific schedule.

Note: You can select only saved reports in a schedule.

See Creating a report schedule in OpsCenter on page 607.

Table 11-6 Steps

Create a time schedule.

Reference topic
See Creating a time schedule on page 611.

Create a time schedule.

Reporting in OpsCenter Reports > Schedules options

603

Table 11-6 Steps

(continued) Reference topic

See Creating a report schedule in OpsCenter on page 607.

Create a report schedule.

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

Report schedule name

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

Select the reports that you want to export or email on a specific schedule.

Note: You can select only saved reports

in a schedule.

Reports > Schedules options

Using report schedules, you can email or export reports at a scheduled time. Each report schedule is associated with a time schedule at which it emails or sends the specified reports. Table 11-7 Option
Add/Edit Delete Enable/Disable

Report Schedules tab options Description

Select Add or Edit to start the Report Schedule Wizard. Select Delete to remove the selected report schedules. Select Enable or Disable to enable or disable the selected report schedules. Name of a report schedule.

Name

604

Reporting in OpsCenter About managing report schedules in OpsCenter

Table 11-7 Option

Report Schedules tab options (continued) Description

Name of a time schedule that is associated with this report schedule. Specifies whether the report schedule is enabled or not. Date on which this schedule runs. Date on which this schedule stops. Specifies whether you have exported the associated reports. Specifies whether you have emailed the associated reports. Number of the reports that are exported or emailed when this schedule runs.

Time Schedule Name

Enabled Start Date End Date Export Email Reports

Table 11-8 Option

Add/Edit Delete Name Schedule Time

Time Schedules tab options Description

Select Add or Edit to go to the Time Schedule page. Select Delete to delete the selected time schedules. Name of the time schedule. Time when the associated reports are exported or emailed. A pattern with which this schedule runs. Date when the schedule starts. Date when the schedule stops.

Recurrence Pattern Start Date End Date

About managing report schedules in OpsCenter

NetBackup OpsCenter provides a way to export or email a report on a specific schedule. For this task you need to create a report schedule that is associated with a time schedule on which the specified reports are exported or emailed. Each report schedule can be associated with a single time schedule. A single time schedule can be associated with multiple report schedules. See About managing time schedules in OpsCenter on page 610. The following topics describe how to create and manage report schedules.

Reporting in OpsCenter About managing report schedules in OpsCenter

605

See Viewing report schedule details in OpsCenter on page 605. See Creating a report schedule in OpsCenter on page 607. See Editing a report schedule in OpsCenter on page 609. See Deleting a report schedule in OpsCenter on page 610. See Enabling or disabling a report schedule on page 610.

Viewing report schedule details in OpsCenter

This section provides information on viewing the list of report schedules. If you have applied conditions for the selected report, the list of applicable conditions is shown on the last page of the wizard. You can select the appropriate conditions. An email notification is sent to the relevant recipients if the selected condition is satisfied. To view report schedule details

In the OpsCenter console, click Reports > Schedules. By default, the Report Schedules tab is selected.

On the Report Schedules tab, view the report schedule details. See Reports > Schedules options on page 603.

Report Schedule Wizard

The Report Schedule Wizards contains five panels to help you create a schedule. Table 11-9 Option
Report Schedule Name Select Format

Enter Report Schedule Details panel options Description

Enter a report schedule name. This field must be filled. Select a file format in which you want to export or email report the associated reports. See File formats available in OpsCenter on page 589.

Table 11-10 Option

Select Time Schedule panel options Description

Select this option if you want a new time schedule to be associated with the report schedule.

Create new Time Schedule

606

Reporting in OpsCenter About managing report schedules in OpsCenter

Table 11-10 Option

Select Time Schedule panel options (continued) Description

Select this option if you want the report schedule to be associated with an existing time schedule

Use existing Schedule

Table 11-11 Option

Export

Select Export/Email Report Options panel options Description

Select this check box if you want to export the reports that are associated with this schedule. See File formats available in OpsCenter on page 589.

Location

Enter a directory path where you want to save the exported report or click Browse to select the desired location. Select this check box if you want to overwrite a file that already exists at the specified location. Select this check box if you want to email the reports that are associated with this schedule. Select email IDs to which you want to email reports. Select email IDs to add in the Cc list of email. Select email IDs to add in the Bcc list email. Type the email subject. For example: Daily Job Count Report Type any other related information.

Overwrite if file exists

Email

To Cc Bcc Subject Message

Table 11-12 Option

Private Reports

Select Reports panel options Description

Select private reports from the list that you want to schedule. You can select both public and private reports. Select public reports from the list that you want to schedule. You can select both public and private reports.

Public Reports

Reporting in OpsCenter About managing report schedules in OpsCenter

607

Table 11-13 Option

Select a report condition to be applied panel options Description

Send email only if the report Check this option if you want the report to be emailed only meets one or more selected if it meets one or more of the selected conditions. You can conditions create conditions for custom reports while editing the report. Report Name The custom reports that have conditions and are selected to be scheduled are displayed. The condition that is associated with the custom report is displayed. You can create a condition only for custom reports.

Condition

Creating a report schedule in OpsCenter

To create a report schedule

1 2

In the OpsCenter console, click Reports > Schedules. On the ReportSchedules tab, click Add. OpsCenter provides a Report Schedule Wizard that guides you through the procedure of creating a report schedule. The Enter Report Schedule Details panel appears as follows:

Enter the report schedule details. See Report Schedule Wizard on page 605.

608

Reporting in OpsCenter About managing report schedules in OpsCenter

Click Next. The Select Time Schedule panel appears:

Select the Use existing schedule option if you want to run this schedule on any existing time schedule. If you want to create a new time schedule for this report schedule, select Create new time schedule. See Creating a time schedule on page 611. If you have selected Create new time schedule, the system takes you to the Time Schedule Wizard. After creating a time schedule you can select the export and the email report options.

4 5

Click Next. If you have selected the Use existing schedule option in the previous step, in the Configure Export/Email Report Settings panel, specify the following details: You can select either Export, Email, or both options. See Report Schedule Wizard on page 605.

Click Next.

Reporting in OpsCenter About managing report schedules in OpsCenter

609

In the Select Reports panel, select the public or private reports that you want to export or email on this schedule. These reports should be saved.

Click Back if you want to change the previous selections.

In the Select a report condition to be applied panel, select a report and report condition to be applied. You can apply report conditions to custom reports. You can also select the option Send email only if the report meets one or more of the selected conditions if you want the report to be emailed only when the report meets one or more of the selected conditions.

Click Save.

Editing a report schedule in OpsCenter

This section describes how to edit report schedule details. To edit a report schedule

In the OpsCenter console, click Reports > Schedules. By default, the Report Schedules tab is selected.

2 3 4 5

On the Report Schedules tab, select a report schedule from the list that you want to edit. Click Edit. Edit the report schedule details using the wizard. Click Save.

610

Reporting in OpsCenter About managing time schedules in OpsCenter

Deleting a report schedule in OpsCenter

This section describes how to delete a report schedule. To delete a report schedule

In the OpsCenter console, click Reports > Schedules. By default, the Report Schedules tab is selected.

2 3

On the Report Schedules tab, select one or more report schedules from the list that you want to delete. Click Delete.

Enabling or disabling a report schedule

This section describes how to enable or disable a report schedule. To enable or disable a report schedule

In the OpsCenter console, click Reports > Schedules. By default, the Report Schedules tab is selected.

2 3

On the Report Schedules tab, select one or more report schedules from the list that you want to enable or disable. Click Enable or Disable.

About managing time schedules in OpsCenter

This section provides procedures to create and manage a report schedule. Each report schedule can be associated with only a single time schedule. A single time schedule can be associated with multiple report schedules. See About managing report schedules in OpsCenter on page 604. The following topics provide more information about managing time schedules. See Viewing time schedule details on page 611. See Creating a time schedule on page 611. See Editing a time schedule on page 612. See Deleting a time schedule on page 612.

Reports > Schedules > Create or Edit Time Schedule options

Use the page to create or edit a time schedule.

Reporting in OpsCenter About managing time schedules in OpsCenter

611

Table 11-14 Option

Schedule Name Schedule Time

Create or Edit Time Schedule options Description

Enter name of the time schedule. Enter the time when the schedule runs and the associated reports are exported or emailed. Select a pattern with which you want this schedule to be run. The following schedule patterns are available:

Schedule Pattern

One Time Daily Weekly Monthly Quarterly Yearly

Depending on the pattern selected, options change.

Viewing time schedule details

This section provides a procedure to view the details of time schedules. To view a time schedule

1 2

In the OpsCenter console, click Reports > Schedules. Click Time Schedules. The time schedule details appear: See Reports > Schedules options on page 603.

Creating a time schedule

Use the following procedure to create a time schedule. To create a time schedule

1 2 3 4

In the OpsCenter console, click Reports > Schedules. Click Time Schedules. On the Time Schedules tab, click Create. On the Create Time Schedule page, specify the necessary details. See Reports > Schedules > Create or Edit Time Schedule options on page 610.

612

Reporting in OpsCenter About Report Templates descriptions

Click OK.

Editing a time schedule

Use the following procedure to edit a time schedule. To edit a time schedule

1 2 3 4 5 6

In the OpsCenter console, click Reports > Schedules. Click Time Schedules. On the Time Schedules tab, in the table, select the time schedule that you want to edit. Click Edit. Edit the time schedule details. Click OK.

Deleting a time schedule

Use the following procedure to delete a time schedule. To delete a time schedule

1 2 3 4

In the OpsCenter console, click Reports > Schedules. Click Time Schedules. On the Time Schedules tab, in the table, select the time schedules that you want to delete. Click Delete.

About Report Templates descriptions

This section provides descriptions of all Report Templates available in OpsCenter. A few important notes on the OpsCenter Report Templates :

The Week at a glance, Drive Throughput, and Drive Utilization reports can be exported and emailed only in the HTML format. The Week at a glance report does not display graphics when it is emailed or exported in an HTML format. A tabular report that is scheduled for emailing can have up to 4000 rows. Exporting a tabular report in the available formats can only display data for a maximum of 4000 rows.

Reporting in OpsCenter About Report Templates descriptions

613

Reports in the PDF, TSV, or CSV formats are sent as email attachments. A report in the HTML format is sent as an inline message in email. Sorting for HTML-based reports (for example, Drive Utilization) is not supported. For the OpsCenter admin, the default view that is selected is All_Master_Server.

See About Enterprise Vault Archiving reports in OpsCenter on page 613. See About Audit reports on page 616. See About Backup reports in OpsCenter on page 617. See About Catalog reports in OpsCenter on page 636. See About Chargeback reports in OpsCenter on page 637. See About Client reports in OpsCenter on page 638. See About Disk and Tape Device Activity reports in OpsCenter on page 644. See About Media reports in OpsCenter on page 647. See About Performance reports in OpsCenter on page 651. See About Policy reports in OpsCenter on page 654. See About Restore reports in OpsCenter on page 657. See About Storage Lifecycle Policy reports on page 657. See About Workload Analyzer on page 693.

About Enterprise Vault Archiving reports in OpsCenter

This section provides descriptions of archive Report Templates available in OpsCenter.
Archive Storage > Archived Count See Archive Storage > Archived Count report on page 614.

Archive Storage > Tabular - Storage Report See Archive Storage > Tabular - Storage Report on page 614. Archive Storage > Archived Size See Archive Storage > Archived Size report on page 614. See Exchange > Mailbox Quota report on page 614. See Exchange > Archive Size Vs Original Size report on page 615.

Exchange > Mailbox Quota

Exchange > Archive Size Vs Original Size

614

Reporting in OpsCenter About Report Templates descriptions

Exchange > Item Count

See Exchange > Item Count report on page 615. See Exchange > Target Report Detail report on page 616. See Exchange > Original Size report on page 616.

Exchange > Target Report Detail

Exchange > Original Size

Archive Storage > Archived Count report

This report shows the number of messages or items that were archived across vault servers, sites, archive targets, provisioning groups, and business level views.

Archive Storage > Tabular - Storage Report

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

Archive Storage > Archived Size report

This report is available only in the Archive Storage report category. Use this report if you want to determine the size of the Exchange Server data that was archived. You can determine the size of the Exchange Server data that was archived and stored in a specific Vault Store, Enterprise Vault Server, or Vault Store Partition. The Archived Size report is available in the Archive Storage report category. The Archive Size Vs Original Size report depicts the difference between the two sizes of Exchange Server data. The more the difference, the more efficient is your archival process.

Exchange > Mailbox Quota report

The Mailbox Quota report displays the top mailboxes in Exchange Server, which have exceeded a particular mailbox size limit. This report is available in the Ranking report view. There are three types of Mailbox Quota reports:

Reporting in OpsCenter About Report Templates descriptions

615

By Warning Limit

This report shows the mailboxes that have exceeded the Warning limit set in Exchange Server. The Warning limit is a limit set for mailboxes, which decides how much data mailboxes can contain. For example: The Warning limit for mailboxes is set to 256 MB. The By Warning Limit report displays all mailboxes that have exceeded 256 MB of data.

By Send Limit

This report shows the mailboxes that have exceeded the Send limit set in Exchange Server. The Send limit is a limit set for mailboxes, which is greater than the Warning limit. If size of a mailbox exceeds this limit, emails cannot be sent from this mailbox.

By Receive Limit

This report shows the mailboxes that have exceeded the Receive limit. If size of your mailbox exceeds the Receive limit, you cannot receive any emails.

The Mailbox Quota reports are available in the Exchange report category.

Exchange > Archive Size Vs Original Size report

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

Exchange > Item Count report

This report is available in both archive report categories, Exchange and Archive Storage. Use this report to determine the number of emails or items in each Exchange Server in an Enterprise Vault environment. The Item Count report is available in all three graphical views, Historical, Ranking, and Distribution. This report provides different drill-down reports depending on the archive report category that you have selected.

616

Reporting in OpsCenter About Report Templates descriptions

Exchange > Target Report Detail report

The Target Details report shows details of all mailboxes in all Exchange Servers in an archive site. The word Target refers to individual mailboxes. The details include the name of a mailbox, original size of emails in a mailbox (Item Original Size), archived size of emails (Item Archived Size), and number of emails (Target Item Count).

Exchange > Original Size report

This report is available only in the Exchange report category. Generate this report if you want to determine the original size of the Exchange Server data that was archived. You can view the original size of the archived data for a specific archive site or Exchange Server. You can also determine the original size of the data that was archived and stored in a specific Vault Store, Enterprise Vault Server, or Vault Store Partition. You can select these filters using the Advanced Filters option on the Report Wizard page. The Original Size report is available in all three graphical views, Historical, Ranking, and Distribution. The following example explains about the original size of the data that was archived:

You have 100 MB of Exchange Server data, which is the total mailbox size Out of 100 MB data you want to archive 30 MB, as per the definition in an archive policy After archiving, the 30 MB data is compressed into 20 MB data The Original Size of Exchange Server data was 30 MB and Archived Size is now 20 MB The total savings are equal to the difference between the Original Size and Archived Size. Total Savings = 30 MB - 20 MB = 10 MB By archiving, you can save on huge amount of storage space.

About Audit reports

This section provides descriptions on the Audit Report Template available in OpsCenter.

Audit Reports > Audit Trails Report

This section provides descriptions on the Audit Report Template available in OpsCenter.

Reporting in OpsCenter About Report Templates descriptions

617

Audit trails is a record of all the user initiated activities. An audit trail consists of the changes that are made in the NetBackup environment. For example, changes such as creating a policy, deactivating a policy, or modifying a policy. You can generate the Audit trails report through the reports tab. You can also create a custom SQL. For example, enter a query: SELECT * FROM audit_record on SQL query page. See Creating an OpsCenter report using a Report Template on page 585. See Creating an OpsCenter report using SQL query on page 592.

About Backup reports in OpsCenter

This section provides descriptions on all backup Report Templates available in OpsCenter.
Deduplication > Deduplication Size Factor > Historical Deduplication > Deduplication Size Factor > Rankings Deduplication > Pre vs. Post Deduplication Size See Deduplication > Deduplication Size Factor > Historical report on page 621. See Deduplication > Deduplication Size Factor > Rankings report on page 621. See Deduplication > Pre vs. Post Deduplication Size report on page 621.

Deduplication > Deduplication Size Savings See Deduplication > Deduplication Size > Historical Savings > Historical report on page 621. Deduplication > Deduplication Size Savings See Deduplication > Deduplication Size > Rankings Savings > Rankings report on page 621. Job Activity > Variance > About Throughput See Job Activity > Variance > About Variance report Throughput Variance report on page 622. Job Activity > Variance > About File Count Variance report Job Activity > Variance > About Backup Duration Variance report See Job Activity > Variance > About File Count Variance report on page 622. See Job Activity > Variance > About Backup Duration Variance report on page 622.

Job Activity > Variance > About Backup Job See Job Activity > Variance > About Backup Size Variance report Job Size Variance report on page 623. Job Activity > Backup Window > Job Count See Job Activity > Backup Window > Job Count report on page 623. See Job Activity > Backup Window > Job Size report on page 623.

Job Activity > Backup Window > Job Size

618

Reporting in OpsCenter About Report Templates descriptions

Job Activity > Backup Window > File Count See Job Activity > Backup Window > File Count report on page 624. Job Activity > Job Count > Distribution See Job Activity > Job Count > Distribution report on page 624. See Job Activity > Job Count > Historical report on page 624. See Job Activity > Job Count > Rankings report on page 624. See Job Activity > Job Size > Historical report on page 624. See Job Activity > Job Size > Rankings report on page 624. See Job Activity > Job Size > Distribution report on page 625. See Job Activity > Client Count > Historical report on page 625. See Job Activity > Client Count > Ranking report on page 625. See Job Activity > Client Count > Distribution report on page 625. See Job Activity > Job Duration > Ranking report on page 625. See Job Activity > File Count > Historical report on page 625. See Job Activity > File Count > Ranking report on page 625. See Job Activity > File Count > Distribution report on page 626. See Job Browser > Tabular Backup Report report on page 626. See Planning Activity > Capacity Planning > Forecasted Size report on page 626. See Planning Activity > Capacity Planning > Historical Size report on page 626.

Job Activity > Job Count > Historical

Job Activity > Job Count > Rankings

Job Activity > Job Size > Historical

Job Activity > Job Size > Rankings

Job Activity > Job Size > Distribution

Job Activity > Client Count > Historical

Job Activity > Client Count > Ranking

Job Activity > Client Count > Distribution

Job Activity > Job Duration > Ranking

Job Activity > File Count > Historical

Job Activity > File Count > Ranking

Job Activity > File Count > Distribution

Job Browser > Tabular Backup Report

Planning Activity > Capacity Planning > Forecasted Size Planning Activity > Capacity Planning > Historical Size

Reporting in OpsCenter About Report Templates descriptions

619

Planning Activity > Forecast > Job Count

See Planning Activity > Forecast > Job Count report on page 627. See Planning Activity > Forecast > Job Size report on page 627. See Planning Activity > Scheduled Job > Scheduled Job report on page 627. See Planning Activity > Scheduled Job > Job Count Scheduled Vs Actual report on page 628. See Planning Activity > Scheduled Job > Job Count within Backup Window report on page 628. See Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report on page 629.

Planning Activity > Forecast > Job Size

Planning Activity > Scheduled Job > Scheduled Job Planning Activity > Scheduled Job > Job Count Scheduled Vs Actual

Planning Activity > Scheduled Job > Job Count within Backup Window

Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual

Planning Activity > Scheduled Job > All Jobs See Planning Activity > Scheduled Job > All Jobs report on page 630. Planning Activity > Stored Backup Images > Valid Backup Images See Planning Activity > Stored Backup Images > Valid Backup Images report on page 631. See Planning Activity > Stored Backup Images > Duplicate Copies report on page 631. See Planning Activity > Stored Backup Images > Stored Backup Images > Historical report on page 631.

Planning Activity > Stored Backup Images > Duplicate Copies

Planning Activity > Stored Backup Images > Stored Backup Images > Historical

Status & Success Rate > Status > Failed Job See Status & Success Rate > Status > Failed Count Job Count report on page 631. Status & Success Rate > Status > Partially Successful Job Count See Status & Success Rate > Status > Partially Successful Job Count report on page 632.

Status & Success Rate > Status > Successful See Status & Success Rate > Status > Job Count Successful Job Count report on page 632. Status & Success Rate > Status > All Failed Backups See Status & Success Rate > Status > All Failed Backups report on page 632.

620

Reporting in OpsCenter About Report Templates descriptions

Status & Success Rate > Status > Consecutive See Status & Success Rate > Status > All Failures Failed Backups report on page 632. Status & Success Rate > Status > Success Rate Line See Status & Success Rate > Status > Success Rate Line report on page 633.

Status & Success Rate > Status > Week At A See Status & Success Rate > Status > Week Glance At A Glance report on page 633. Status & Success Rate > Status > Backup Window Failures Status & Success Rate > Status > Partially Successful Job Details See Status & Success Rate > Status > Backup Window Failures report on page 633. See Status & Success Rate > Status > Partially Successful Job Details report on page 633. See Status & Success Rate > Status > Skipped Files Summary report on page 634. See Status & Success Rate > Status > Job Exit Status Detail report on page 634.

Status & Success Rate > Status > Skipped Files Summary Status & Success Rate > Status > Job Exit Status Detail

Status & Success Rate > Status > Job Details See Status & Success Rate > Status > Job Details report on page 634. Status & Success Rate > Status > Job Summary by Status See Status & Success Rate > Status > Job Summary by Status report on page 634.

Status & Success Rate > Status > Job Status See Status & Success Rate > Status > Job > Historical Status > Historical report on page 635. Status & Success Rate > Status > Job Status See Status & Success Rate > Status > Job > Distribution Status > Distribution report on page 635. Status & Success Rate > Success Rate > Success Rate All Jobs Status & Success Rate > Success Rate > Advanced Success Rate Status & Success Rate > Success Rate > Success Rate All Attempts See Status & Success Rate > Success Rate > Success Rate All Jobs report on page 635. See Status & Success Rate > Success Rate > Advanced Success Rate report on page 635. See Status & Success Rate > Success Rate > Success Rate All Attempts report on page 636. See Status & Success Rate > Success Rate > Success Rate - First Attempt report on page 636.

Status & Success Rate > Success Rate > Success Rate - First Attempt

Reporting in OpsCenter About Report Templates descriptions

621

Deduplication > Deduplication Size Factor > Historical report

This report is usually the most talked about when it comes to deduplication since it shows what the deduplication ratio is for each day over the last two weeks (the time frame is modifiable). The deduplication ratio is calculated by taking the total number of bytes that would normally be backed up and dividing it by the number of bytes that have changed and were backed up. So if 100TB exists on all the backups taking place but only 10TB were changed and therefore transferred, you have a rate of 10. This report shows only deduplication jobs. The default Report On parameter for this report is Master Server. This report is available in a line-chart format.

Deduplication > Deduplication Size Factor > Rankings report

This deduplication report ranks the top hosts in terms of which ones have the best deduplication ratio in bytes. These hosts have the least amount of change and therefore you get the best benefit from deduplication. This report shows only deduplication jobs. The default Report On parameter for this report is Master Server.

Deduplication > Pre vs. Post Deduplication Size report

The report gives the comparison between the total number of bytes that exist on all the backups as if they were normal full backups and the number of bytes that have changed and therefore needed to be transferred. This report shows only deduplication jobs. The default Report On parameter for this report is All Master Servers.

Deduplication > Deduplication Size Savings > Historical report

This report shows the total number of bytes that do not need to be backed up because of deduplication. There is no calculation or ratio in this number. It is the number of bytes (MB, GB, TB etc.) that have not changed since the last backup and therefore dont need to be backed up. This report shows only deduplication jobs. The default Report On parameter for this report is Master Server.

Deduplication > Deduplication Size Savings > Rankings report

This report shows the number of bytes that have not changed within the time frame and therefore do not have to be backed up due to deduplication. The report

622

Reporting in OpsCenter About Report Templates descriptions

groups the total number of bytes saved per host being backed up to show the top five hosts in terms of deduplication savings. This report shows only deduplication jobs. The default Report On parameter for this report is Master Server.

Job Activity > Variance > About Throughput Variance report

This report provides an indication of how throughput (in MB per second) for a backup varies from the average throughput for a particular policy, client, and schedule type. You can detect any anomalies if the variation is too high. This report calculates the backup throughput variation of the last good backup with the average backup throughput per a server, client, policy, and schedule type. If any variation calculation is greater than the selected value of variance when the report is run, the client, policy and schedule type combination is shown in the table with the actual variation. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame.

Job Activity > Variance > About File Count Variance report
This report lets you investigate why a particular full backup is different than usual. For example, a file server backup is successful, but contains fewer files than usual for a full backup. The report shows NetBackup jobs with significant differences in file counts from the average count for a master server, policy, and schedule. If any variation calculation is greater than the selected value of variance when the report is run, the server, client, policy, and schedule type combination is shown with the actual file count variation. The table provides the percent variance (in file counts) for each good job from the average for that server, policy, and schedule. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame.

Job Activity > Variance > About Backup Duration Variance report
This report provides an indication of how backup time varies from the average backup time. You can detect any anomalies if the variation is too high. This report calculates the backup time variation of the last good backup with the average backup time per client, policy, and schedule type. If any variation

Reporting in OpsCenter About Report Templates descriptions

623

calculation is greater than the selected value of variance when the report is run, the client, policy, and schedule type combination is shown with the actual variation.

About client jobs for selected time frame report

This drilldown report from the Client Name column provides detailed job information for the client for the selected time frame. This drilldown report uses the run time parameters that are passed from the main report.

Job Activity > Variance > About Backup Job Size Variance report
This report provides an indication of how a backup size varies from the average size. You can detect any anomalies if the variation is too high. This report calculates the backup size variation of the last good backup with the average backup size per a client, policy, and schedule type. If any variation calculation is greater than the selected value of variance when the report is run, the client, policy and schedule type combination is shown with the actual variation. Size variance is calculated using the following formula: (the last backup size - the average backup size) / the average backup size x 100. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame.

Job Activity > Backup Window > Job Count report

This report shows the total number backup jobs in the last two weeks shown by the hour of the day in which each job ends. It also renders a configurable backup window to help quickly identify if a lot of jobs end in or outside of what your backup window is or should be. The report can help you see if there are any hours within the backup window that are under used and whether any load balancing is appropriate. In OpsCenter, the Job Count report does not include the jobs that were collected during the image data collection. These jobs are called Sparse Jobs. This is unlike the Job Count report in VBR, which also included Sparse Jobs. Because of this change, you may notice a mismatch between the job count on the OpsCenter report and the corresponding VBR report.

Job Activity > Backup Window > Job Size report

This report shows the total gigabytes backed up in the last two weeks shown by the hour of the day in which each job ends. It also renders a configurable backup

624

Reporting in OpsCenter About Report Templates descriptions

window to help quickly identify if a lot of jobs end in or outside of what your backup window is or should be. The report can help you see if there are any hours within the backup window that are under used and whether any load balancing is appropriate.

Job Activity > Backup Window > File Count report

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

Job Activity > Job Count > Distribution report

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

Job Activity > Job Count > Historical report

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

Job Activity > Job Count > Rankings report

This report shows you the top 10 largest environments by ranking the total number of jobs that are performed by each media server for the past two weeks.

Job Activity > Job Size > Historical report

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

Job Activity > Job Size > Rankings report

This report shows you the top 10 largest backup clients by ranking them on the total number of gigabytes backed up for that client in the specified time frame.

Reporting in OpsCenter About Report Templates descriptions

625

The report can give you an idea of your top consumers and whether those consumers are what you expected.

Job Activity > Job Size > Distribution report

This report gives you a breakdown by each media server of the total gigabytes theyve backed up over the specified time frame. It shows a clear distribution of the amount of data going to all your media servers and whether any type of load balancing might be beneficial.

Job Activity > Client Count > Historical report

This report shows the total number of unique clients that are backed up per day for the specified time frame broken down by each master server. It can help you highlight potential problems by showing any variations in the number of clients that you think should be backed up and how many are in fact getting backed up.

Job Activity > Client Count > Ranking report

This report shows you the top 10 largest environments by listing the number of unique clients that got backed up per each media server in your environment for the specified time frame.

Job Activity > Client Count > Distribution report

This report gives you a breakdown by each master server of the number of unique clients that got backed up in the specified time frame.

Job Activity > Job Duration > Ranking report

This report shows you the top 10 highest clients that are ranked by the total amount of time they were backed up for specified time frame.

Job Activity > File Count > Historical report

This report shows you the total number of files that got backed up for each day in specified time frame for each of your master servers. Unexpected variations in this report between your day-to-day incremental or between full backup cycles can indicate problems.

Job Activity > File Count > Ranking report

This report shows you the top 10 largest backup clients. The report ranks them on the total number of files that were backed up for them for specified time frame.

626

Reporting in OpsCenter About Report Templates descriptions

Job Activity > File Count > Distribution report

This report gives you a breakdown by each master server of the total number of files that got backed up in specified time frame.

Job Browser > Tabular Backup Report report

This report shows you a detailed listing of all the backup activity that is performed for the past two weeks. You can edit the report to show or hide the columns you are interested in. You can also filter the report to show activity for a limited sample set, such as one or more policies or clients.

Planning Activity > Capacity Planning > Forecasted Size report

This report shows the supply vs. demand historically but also adds a forecast line for both supply and demand that can show when in the future they may meet. The point that these two lines intersect would be the date that new capacity (more disk or more backup tapes) needs to be added. In the above example the supply is by far outgrowing the demand, which would suggest that more capacity does not need to be purchased. The default first view of this report shows the entire backup environment but for actual use it should be filtered to a specific tape library or disk pool since some libraries or pools may be closer to full capacity than others.

Planning Activity > Capacity Planning > Historical Size report

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

Reporting in OpsCenter About Report Templates descriptions

627

Planning Activity > Forecast > Job Count report

This report shows you the total number of backup jobs for each day in specified time frame. A linear regression forecast is also performed to show you how many backups you can expect for the next three days based on the current data.

Planning Activity > Forecast > Job Size report

This report shows you the total gigabytes backed up for each week in the past two months. A linear regression forecast is also performed to show you how much you can expect to be backed up for the next few weeks on the current data.

Planning Activity > Scheduled Job > Scheduled Job report

This report is available in Ranking Report view, which depicts how many jobs have been scheduled to run in future. You can view the Scheduled Jobs per schedule, policy, master server, or client. Note: By default, the Scheduled Jobs report shows job count per policy. If you want to view the job count for clients, schedules, or master servers, change the report parameters. There is more information available about how to change this report's parameters. See Changing the Planning Activity > Scheduled Job > Scheduled Job report parameters on page 627.

Changing the Planning Activity > Scheduled Job > Scheduled Job report parameters
To change the report parameters

1 2 3

On the Scheduled Jobs report, click the Edit link. On the Report Wizard, from the Report On drop-down list, select a Scheduled Job attribute. For example: Client, Master Server, Policy, or Schedule Name. Click Run.

Note: To view job count for a specific client, policy, master server, or schedule, click Show Advanced Filters and select name of the client, policy, master server, or schedule, for which you want to view job count. There is more information about the Planning Activity > Scheduled Job > Scheduled Job report.

628

Reporting in OpsCenter About Report Templates descriptions

See Planning Activity > Scheduled Job > Scheduled Job report on page 627.

Planning Activity > Scheduled Job > Job Count Scheduled Vs Actual report
This historical report depicts how many jobs were scheduled to run in future and how many jobs are run. The report essentially shows the comparison between Scheduled (Future) Job Count and Actual Job Count. Using this report you can determine whether the jobs that were scheduled to run in future have been run on schedule. There is more information available about how to exclude manual jobs from the actual job count. See Excluding manual jobs from the actual jobs in the Job Count Scheduled Vs Actual report on page 628.

Excluding manual jobs from the actual jobs in the Job Count Scheduled Vs Actual report
By default the Actual Job Count includes manual jobs, which were initiated manually by NetBackup admin. To exclude manual jobs from the Actual Job count, and view only those jobs that have execution type as Scheduled, do the following: To exclude manual jobs from the actual jobs

1 2 3

On the Job Count-Scheduled Vs Actual report, click the Edit link. On the Report Wizard, in the Filter Options section, select Yes from the Exclude Manual Jobs drop-down list. Click Run.

There is more information available about the Planning Activity > Scheduled Job > Job Count Scheduled Vs Actual report. See Planning Activity > Scheduled Job > Job Count Scheduled Vs Actual report on page 628.

Planning Activity > Scheduled Job > Job Count within Backup Window report
This historical report depicts how many jobs were scheduled and how many jobs have been run within the specified backup window. The report essentially shows the comparison between Scheduled (Future) Job Count and Actual Job Count, during the backup window.

Reporting in OpsCenter About Report Templates descriptions

629

Use this report to determine whether your backup windows are appropriate and are properly used.

Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report
This tabular report shows the comparison between Scheduled Job count and Actual Job count for each of the combinations of clients, policies, and schedules, for each day. Note: By default, the Job Count Details-Scheduled Vs Actual report shows job count per policy. If you want to view the job count per client or master server, change the filter parameters. There is more information available about modifying the Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report. See Modifying the Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report on page 629.

Modifying the Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report
Note: By default, the Job Count Details-Scheduled Vs Actual report shows job count per policy. If you want to view the job count per client or master server, change the filter parameters. To change the report parameters

1 2 3 4

On the Job Count Details-Scheduled Vs Actual report, click the Edit link. On the Report Wizard, in the Define Viewable Columns section, select a column name (Client or Master Server) from the Available Columns list. Click >> option. Click Run.

Note: To view job count for a specific client, policy, master server, or schedule, click Show Advanced Filters. Then select the name of the policy, master server, or schedule for which you want to view job count. By default the jobs that were run (Actual Job Count) include manual jobs, which do not have any schedule time associated with them as they are initiated manually.

630

Reporting in OpsCenter About Report Templates descriptions

You can exclude manual jobs from the actual job count, and view only the jobs that are of execution type Scheduled. To exclude manual jobs from the actual jobs

1 2 3

On the Job Count Details-Scheduled Vs Actual report, click the Edit link. On the Report Wizard, in the Filter Options section, select Yes from the Exclude Manual Jobs drop-down list. Click Run.

The Job Count Details-Scheduled Vs Actual report shows comparison between Scheduled Job count and Actual Job count. The Actual Job count includes Manual Jobs. There is more information available about the Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report. See Planning Activity > Scheduled Jobs > Job Details Scheduled Vs Actual report on page 629.

Planning Activity > Scheduled Job > All Jobs report

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

Note: While generating the Job Count-Scheduled Vs Actual report,

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

Reporting in OpsCenter About Report Templates descriptions

631

Planning Activity > Stored Backup Images > Valid Backup Images report
This report shows unexpired backup images across products, domains, clients, policies, and business level views. This report is valid only for NetBackup. This report is available in Ranking and Distribution views.

Planning Activity > Stored Backup Images > Duplicate Copies report
The axis on the left is for the height of the blue bars for example that tells the number of duplicate backup copies that exist overall. The yellow line for example is the axis on the right and it shows the percentage of backup images that are copies. This is a particularly useful report for situations where you want to make certain there is always more than 1 backup copy. If two copies of a backup exist, the blue bar would be a height of 1 (since there is 1 extra copy) and the line would show .5 for 50% since half of the backup images are copies. The same situation for 3 copies would be a blue bar height of 2 and a yellow line percentage of .66 or 66%. In operational use you can filter this report down to specific policies or the clients that you want to ensure always have a 50% or greater yellow line so that more than 1 backup copy exists.

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

Status & Success Rate > Status > Failed Job Count report
This report aggregates failed jobs and shows these across a timeline. In reality, this report is the same as all jobs as no distinction on whether the failed job was first or last one is made. It provides visualization of whether a problematic trend exists. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The primary use case of the report is verification of whether actions taken to correct persistent failures produce results and reversing trends.

632

Reporting in OpsCenter About Report Templates descriptions

Status & Success Rate > Status > Partially Successful Job Count report
This report aggregates partially successful jobs and shows these across a timeline. It provides a visualization of job volume trends that skip the files that are open during the backup job. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The primary use case of the report is verification of whether actions taken to correct the open file situation by moving the scheduling of the client or policies produce results and reversing trends.

Status & Success Rate > Status > Successful Job Count report
This report aggregates successful jobs and shows these across a timeline. It provides a visualization of job volume trends. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The primary use case of the report is verification of trends and the days that are exception to the norm. The report is highly effective for presenting long-term historical data on one of the most fundamental metrics of managing a backup operation.

Status & Success Rate > Status > All Failed Backups report
This report is one of three using the advanced success or failure calculation logic around the notion of first, all and last job. They require schedule and window parameters enabling a precise definition of timeframes. Additionally, these reports have aggregation levels of job and client. The first job success or failure is the first job for a client/policy/schedule combination in its defined backup window and last job is the opposite. As failed jobs are rerun one or more times, the last job represents the last of the reruns within the window. This report produces the details of the failed jobs based on which one of the three (first or all or last) methods is chosen. The main use case for this report is based on last job where failure notification to users is based around last job and failures leading up to the last one is ignored.

Status & Success Rate > Status > Consecutive Failures report
This report is the second of three using the advanced success or failure calculation logic around the notion of first, all and last job. The main use case is the calculation of 2 or more consecutive failures based around Last Job Success/Failure. It applies

Reporting in OpsCenter About Report Templates descriptions

633

intricate logic to pick off the last failed job and in turn to determine that the last job failures are indeed consecutive. This report can be best verified through the Client Risk Analysis report. In this report, if three consecutive failures with 24 hour windows were chosen, the client or the policy combo should also appear on the risk report as not having a successful backup in 72 or more hours.

Status & Success Rate > Status > Success Rate Line report
This report is a historical report that shows success rate across products, domains, clients, policies, and business level views.

Status & Success Rate > Status > Week At A Glance report
This report summarizes activity for a week by symbolically displaying the result of each job for each client under the day of the week. The symbols are the blue (Success) and yellow (Partial Success) men and failures that are denoted by a red X. A drill-down capability to the job level details (i.e Job ID, Start/End Time, Size etc.) is provided. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The report is highly effective as it provides a visualization of job status for the most current data and how that compares to the previous six days. Week at a Glance Reports performance declines as the data to be displayed in the report increases. For example, running a two-month report is slower than running a two-week report. Note: The Week at a glance report does not display graphics when it is emailed or exported in an HTML format.

Status & Success Rate > Status > Backup Window Failures report
This report lists the jobs which were scheduled to run but failed because the scheduled backup window was no longer open (the NetBackup status code is 196).

Status & Success Rate > Status > Partially Successful Job Details report
This report provides details for all NetBackup partially successful jobs. Partially successful jobs have an exit status of 1. The table in the report is organized by job ID, server name, and client name.

634

Reporting in OpsCenter About Report Templates descriptions

Status & Success Rate > Status > Skipped Files Summary report
The information in this report is presented using a set of linked reports. The main report that is organized by master server, displays clients and policies, and the corresponding number of files that were skipped.
Skipped file details for client report This drilldown report from the Client Name column identifies risks to the client because of any skipped files. This drilldown report uses the run time parameters that are passed from the main report. Skipped file details for policy report This drilldown report from the Policy Name column identifies risks to the client due to any skipped files. This drilldown report uses the run time parameters that are passed from the main report. Skipped file details for policy and client This drilldown report from the No. of Skipped report Files column provides the names of all skipped files. This drilldown report uses the run time parameters that are passed from the main report.

Status & Success Rate > Status > Job Exit Status Detail report
This report provides information about the completion status for a NetBackup job. The report table provides a count of jobs having a particular exit status on a particular day. The table is organized by server name and date. A drilldown report is available from the Number of Occurrences column of the table of the main report. This drilldown report shows job details, such as job type and policy name. The table includes all jobs having a particular exit status on a given day.

Status & Success Rate > Status > Job Details report
This report provides detailed information about NetBackup jobs.

Status & Success Rate > Status > Job Summary by Status report
This report summarizes NetBackup jobs based on the job exit status for a specified time interval. You can use this report to provide trend information. The bar chart shows a count of successful, partially successful, and failed jobs per a given date.

Reporting in OpsCenter About Report Templates descriptions

635

Status & Success Rate > Status > Job Status > Historical report
A job status report in red (failure), yellow (partial success) and green (success) displayed in stacked bar format that is grouped by hour, day, week, month, or year across any timeframe. The report is a count of jobs for each of the three outcomes. The simplicity of the presentation helps easily identify both positive and negative trends as well as one-off deviations. For NetBackup environments, the report can also be generated where attempts rather than jobs are counted. In NetBackup, jobs can be configured for x many attempts before you exit with a status. The report can be filtered across a selection that includes Views, Backup and Media Servers, Backup Level, Policies, Schedules, Transport Types, Operating Systems, and Business Classifications.

Status & Success Rate > Status > Job Status > Distribution report
A job status report in red (failure), yellow (partial success) and green (success) displayed in pie chart format. The report is a count of jobs for each of the three outcomes. The main use cases of the report are typically short-term verification (i.e. last 24 48 hours) of backup job status and long term (i.e. 1+ months) management level reporting requiring high-level status summaries. The report can be filtered across a selection that includes Views, Backup and Media Servers, Backup Level, Policies, Schedules, Transport Types, Operating Systems, and Business Classifications.

Status & Success Rate > Success Rate > Success Rate All Jobs report
This last of the single-line success rate reports give the highest number since it shows at least one success per client stream. Meaning as long as one job is successful despite any number of retries, it is a 100% success. This report typically shows overall exposure to someone outside the backup team. A 100% on this report indicates that everything was backed up even though it may have taken a number of retries.

Status & Success Rate > Success Rate > Advanced Success Rate report
This report uses the advanced success or the failure calculation logic around the notion of first, all and last job. It collects all information around both successes and failures and presents the results that are grouped by (day or month) timeframe for either client or the job success rate. Client success rate is a count of successful clients where all policies that are defined to the client must be successful to declare the client successful. Thus a client is either 0% or 100% and no intermediate state.

636

Reporting in OpsCenter About Report Templates descriptions

Job success rate is derived from all jobs and separated out by first, all and last and a specific client can have a job success rate that can range between 0% and 100%. End-user and customer typically get Last Job Success for job and client whereas back up architects and administrators examine all three. These reports work well with views and can be reported on at any level with robust filtering capabilities.

Status & Success Rate > Success Rate > Success Rate All Attempts report
This report shows success rate as its aggregated at the attempt ( try) level. Jobs can be configured for x many attempts before exiting with a status. If for example the attempt setting is two and success is attained on the second attempt, this translates into a 50% attempt rate and 100% job success rate. This metric is only supported for backup applications in which attempt level data is available. A target line is also supported providing for an effective visual presentation on when the target is exceeded. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. Main use case is long-term historical data on one of the key performance indicators.

Status & Success Rate > Success Rate > Success Rate - First Attempt report
This report shows success rate as it is aggregated at the attempt (known as try) level. Specifically, it zooms in on the measurement of the first attempt for each job. Jobs can be configured for x many attempts before you exit with a status. If for example the attempt setting is two and success is attained on the second attempt, this data translates into a 50% All Attempt rate and 0% First Attempt rate and 100% job success rate. This metric is only supported for backup applications in which attempt level data is available. A target line is also supported providing for an effective visual presentation on when the target is exceeded. Filtering is available on all components and attributes. Main use case is to use this report and the All Attempts report together to see how often success is attained on the first attempt as opposed to second, third etc. attempts.

About Catalog reports in OpsCenter

This section describes catalog reports.

Cold catalog backup report

This report shows the count of cold NetBackup catalog backups and information about the media that NetBackup uses for offline backups.

Reporting in OpsCenter About Report Templates descriptions

637

Tool tips in the bar chart show the report name and backup count. The table in the report also lists the media that NetBackup uses for the backups for each master server.

About Chargeback reports in OpsCenter

This section provides descriptions of chargeback reports.
Deduplication Chargeback report See Deduplication Chargeback report on page 637. See Cost Tabular report on page 637. See Chargeback report on page 637.

Cost Tabular report Chargeback report

Deduplication Chargeback report

This report shows the savings that is achieved because of the deduplication technology. To generate this report, you need to have a cost variable of Protected Job Size. The deduplication technology can identify files and the data segments that contain identical data and treats them as a single instance of the file, which it backs up only once. For example, PureDisk has backed up 100 MB data , in which 20 MB of data is duplicate or identical. PureDisk protects the same data but eliminates the duplicity using deduplication. Therefore, the data that is protected is 100 MB, but the actual data that is backed up by PureDisk is 80 MB, as 20 MB of data is duplicate data. This results in saving 20 MB of data. You can generate the Savings report that shows the amount you have saved using deduplication. The Savings report is available in Distribution, Historical, and Ranking views.

Cost Tabular report

This report shows the chargeback of your backup services in a tabular form. OpsCenter provides organizations with a tool to evaluate the cost of the IT services they consume, which is called Chargeback. You can create cost variables and the formulas that enable you to run the reports that show costs of backup services. To generate the Cost report you need to have a cost formula created.

Chargeback report
This report shows the chargeback of your backup services in Historical and Ranking views. You need to have a cost formula created to generate this report.

638

Reporting in OpsCenter About Report Templates descriptions

About Client reports in OpsCenter

This section describes client reports.
Risk Analysis > Client Risk Analysis See Risk Analysis > Client Risk Analysis report on page 638. See Risk Analysis > Client Coverage report on page 639. See Risk Analysis > Recovery Point Objective report on page 639. See Clients not backed up report on page 639. See Virtual Client Summary report on page 639. See Job success by client report on page 641. See Client summary dashboard report on page 642. See Client restore report on page 643. See BMR client configuration backup failures report on page 643. See Jobs by application report on page 644.

Risk Analysis > Client Coverage

Risk Analysis > Recovery Point Objective

About clients not backed up report

Virtual Client Summary

About job success by client report About client summary dashboard report

About client restore report About BMR client configuration backup failures report About jobs by application report

Risk Analysis > Client Risk Analysis report

This report identifies the backup clients that have gone without a successful backup for a specified period of time and hence are at risk from a restore standpoint or recoverability standpoint. The specified period of time is userdefinable along with several other variables for filtering purposes. The report is interpreted as all client or policy combinations that have gone x hours, days, weeks, or months without a successful backup. The level of granularity is at a client level or policy level and exposes the clients that have multiple backup policies where one of them may repeatedly fail. The primary use case is to show that all clients have been backed up as of the last x hours and all clients have a full backup not more than x days ago. The report also has an Is Active filter to include only those that are currently active as well as the capability to count partial successes as success and vice versa.

Reporting in OpsCenter About Report Templates descriptions

639

Risk Analysis > Client Coverage report

The purpose of this report is to show what hosts are not backed up because the backup application is not even aware of them. The report compares what OpsCenter hosts are known to be backed up with an external list that is fed in by .csv or .tsv. The list can come from a content management database (CMDB), DNS listings or any other authoritative source of what hosts should be backed up. The report works across all backup applications and shows you what backup application and policy executed the backup and the time of the last full or incremental backup.

Risk Analysis > Recovery Point Objective report

- RPO Recovery Point Objective (RPO) and Recovery Time Objective (RTO) have emerged as generally accepted metrics for client recoverability. This report ranks all clients by the amount of time that is elapsed since their last successful backup. In contrast to the Client Risk Analysis report, the level of granularity is the client level and thus clients with multiple backup policies are represented by the policy with most recent success. It is recommended that this report not be used for multi-policy clients. The client Is Active filter allows for those hosts that are not actively backed up to be omitted. The elapsed time in the report is always between now and the last successful backup. The report is effective in its graphical rankings format placing the clients with longest elapsed time at the top.

Clients not backed up report

This report provides a list of NetBackup clients that have not been backed up or clients having all backups fail during the reporting period. You can determine if all jobs of a policy and client combination have failed or have not been initiated during the reporting period. You can filter by type of policy like SharePoint, Oracle, Windows NT and so on. The client name is displayed multiple times in the report if the client has multiple NetBackup policies that are associated with it and none of the policies are run during the reporting period. The report shows details like policy name, schedule name, and date of the last successful backup.

Virtual Client Summary report

The Virtual Client Summary report shows details of all virtual clients of a NetBackup Master Server. Using this report, you can determine whether these virtual clients were backed up by NetBackup or not. Thus, you can report on the virtual clients that need to be protected. You can also drill down in this report to see the job details of a specific virtual client. The Virtual Client Summary report shows the following details:

640

Reporting in OpsCenter About Report Templates descriptions

Virtual Server Name

Name of the virtual server host such as VMware or Hyper-V server Name of the proxy server host that provides details of the virtual clients to the NetBackup Master Server In case of a Hyper-V type of virtual server, the Backup Proxy Name is the same as the Virtual Server Name.

Backup Proxy Name

Virtual Client Name

Name of the virtual client running on a virtual server and which is connected to the NetBackup Master Server through a proxy server Virtual clients are the physical partitions of a virtual server, such as VMware or Hyper-V. Multiple virtual clients may have the same IP address. But they can be identified by their UUIDs. UUID is a unique identifier of a virtual client.

Note: Click the virtual client name link to view

its job details. UUID IP Address Type A unique identifier of the virtual client IP address of the virtual client Type of the virtual server that this client belongs to, such as VMware or Hyper-V Name of the NetBackup Master Server, which backs up this virtual client This field is shown blank if this virtual client is not backed up by any NetBackup Master Server Exists in a Policy This status field that describes whether backing up this virtual client is defined in any NetBackup policy or not If a NetBackup Master Server backs up this client, this field displays Yes. If it shows No, it means that this client should be backed up and be protected. Last Backup Time Time when this virtual client was backed up last This field displays NA (not applicable) if the client is not defined in a backup policy or it is yet to be backed up.

Server Name

Reporting in OpsCenter About Report Templates descriptions

641

Note: The Virtual Client Summary report may give inaccurate results when you configure a NetBackup policy for backing up a VMWare client using a name other than a display name. This happens when you provide names like UUID, DNS, or host name in the Client Selection drop-down list. If you provide a UUID, DNS, or host name in the Client Selection drop-down list, you must use object merger functionality to merge these clients.

Job success by client report

This report shows the rate of success for client jobs. The bar chart shows totals for successful, partially successful, and failed jobs for each client for the selected server or server group. Tool tips in the bars show these job counts. The tool tips for each client also include links to a drill-down report showing details for all job types. The table in the report summarizes job information (including the number of successful and partial successful jobs, and the job success rate). The table is organized by master server and client. The Client Name, Number of Successful Jobs, Number of Partially Successful Jobs, and Number of Failed Jobs columns provide drill down links to more detailed reports.
Job details by client report This drilldown report from the Client Name column or a bar chart tool tip lists all the jobs for the selected client and time frame. The table includes details such as, job type, exit status, and media server name. This drilldown report uses the run time parameters that are passed from the main report. Successful job details for client report This drilldown report from the Number of Successful Jobs column shows details for this job type for the selected client. This drilldown report uses the run time parameters that are passed from the main report. Partially successful job details for client This drilldown report from the Number of Partial report Successful Jobs column shows details for this job type for the selected client. This drill-down report uses the run time parameters that are passed from the main report.

642

Reporting in OpsCenter About Report Templates descriptions

Failed job details for client report

This drilldown report from the Number of Failed Jobs column lists the failed jobs for the selected client. Any jobs with an exit status other than 0 or 1 are considered to be failed jobs. This drilldown report uses the run time parameters that are passed from the main report.

Client summary dashboard report

This report summarizes several parameters for each client for the selected server context and acts as a dashboard of NetBackup activities. You can use drilldown links to view client detail reports for many of the columns in the table. The drilldown reports provide information about the client and answer the following questions:

What is the server name, IP address, and operating system type? How much volume for a client is backed up? How many successful, partially successful, and failed jobs for the client? What is the number of restore jobs that run for the client? What is the average job throughput?

The report can also be used as a tool to monitor the health of backup activities for your managed clients.
Total jobs for client report This drilldown report from the Number of Total Jobs column lists all the jobs for the selected client and time frame. The job details include policy name, schedule name, and throughput (KB/sec). This drilldown report uses the run time parameters that are passed from the main report. Successful jobs for client report This drilldown report from the Number of Successful Jobs column lists the successful jobs for the selected client and time frame. The report lists job details, such as, job type, policy name, start and end times, and job duration. This drilldown report uses the run time parameters that are passed from the main report.

Reporting in OpsCenter About Report Templates descriptions

643

Partially successful jobs for client report

This drilldown report from the Number of Partial Successful Jobs column shows the partially successful jobs for the selected client and time frame. The report lists job details, such as, job type, policy name, start and end times, and job duration. This drilldown report uses the run time parameters that are passed from the main report.

Failed jobs for client report

This drilldown report from the Number of Failed Jobs column lists the failed jobs for the selected client and time frame. Any jobs with an exit status other than 0 or 1 are considered to be failed jobs. The report lists job details, such as, job type, policy name, start and end times, and job duration. This drilldown report uses the run time parameters that are passed from the main report.

Restore jobs for client report

This drilldown report from the Number of Restore Jobs column lists restores job details for the selected client. It provides details like policy name, schedule name, and throughput (KB/sec). This drilldown report uses the run time parameters that are passed from the main report.

Client restore report

This report provides restore job details for a specified client. The table in the report contains information, such as, master and media server names, and start and end times.

BMR client configuration backup failures report

If a NetBackup policy has the Collect BMR Info flag set, the job backs up BMR (Bare Metal Restore) client configuration. This job type starts one or more dependant jobs to back up the client data. This report shows all jobs that failed to completely back up a BMR client configuration, but their related child jobs (client data backup jobs) were partially or fully successful.

644

Reporting in OpsCenter About Report Templates descriptions

Jobs by application report

This report uses the NetBackup policy type to simulate an application level report. For example, an Oracle policy type implies an Oracle application. The report then lets you see all Oracle backups. The table in this report organizes jobs in the table by server, client, and application and includes the backup size in MBs and the number of files. The Application (policy type) column provides a drilldown link to job details for the respective application. There is a drilldown report available from the Application column of the table of the main report. This drilldown report lists all the jobs for the selected client and policy type. The table includes job details such as, job ID, exit status, and job start and end times, and a count of files. This drilldown report uses the run time parameters that are passed from the main report.

About Disk and Tape Device Activity reports in OpsCenter

This section describes disk and tape device activity reports.
Current disk usage report NetBackup Disk Pool Capacity report See Current disk usage report on page 644. See NetBackup Disk Pool Capacity report on page 645.

NetBackup Disk Pool Size vs. Percentage Full See NetBackup SAN Client Performance report report on page 645. NetBackup SAN Client Performance report Library Summary report Library Capacity Forecast report See Current disk usage report on page 644. See Library Summary report on page 645. See Library Capacity Forecast report on page 646. See Drive Throughput report on page 646. See Drive Utilization report on page 646. See SAN client jobs report on page 647.

Drive Throughput report Drive Utilization report SAN client jobs report

Current disk usage report

This report shows the master servers that have disk pools configured. It provides details about the disk pool usage and also how much free space is available in the disk pool.

Reporting in OpsCenter About Report Templates descriptions

645

NetBackup Disk Pool Capacity report

This report is specific to NetBackup 6.5 and above which introduced Disk Pools as a type of Storage Unit. The basic version of this report shows the total amount of space that is occupied by backups across all NetBackup 6.5 Disk Pools which would include OpenStorage Devices, PureDisk deduplication option storage, SharedDisk, or even AdvancedDisk pools. Along with usage the average of the high and the low water mark is taken for each disk pool and drawn on the graph. Since this is an average it should not be used for planning purposes but rather estimation. In actual usage this report should be filtered on a specific Disk Pool to show the exact high and low water mark. Finally the forecast is shown so that it can be determined when capacity needs to be added or backups expired to maintain operations.

NetBackup Disk Pool Size vs. Percentage Full report

This report is specific to NetBackup 6.5 and above which has new devices and storage units called Disk Pools. A Disk Pool may be an OpenStorage device, a PureDisk Deduplication system, SharedDisk, or a group of local or network disk volumes that are pooled together. The bars represent the total number of available bytes across all disk pools with the colors representing the total amount of space per disk pool. The lines represent the percentage full each disk pool is. So this report can help identify how much disk space is used for backups, which pools are the largest, which ones are near capacity and how the backup environment is load balancing across disk storage.

NetBackup SAN Client Performance report

This report is specific to NetBackup 6.5 and above which features Fibre Channel connected clients called SAN Clients. The blue and the yellow bars for example are stacked together to show the total number of jobs per day. The blue bars represent the jobs that ran over the LAN and the yellow is jobs ran over the SAN. The purple and the yellow lines show the total job throughput for all those jobs that ran that day. The purple represents total job throughput by LAN and the yellow represents total job throughput by SAN. This report helps identify what ratio of LAN to SAN traffic for backups are run and what performance benefit is gained by doing so.

Library Summary report

This report provides a current point in time inventory of library capacity. The reports list the libraries name, Volume DB Server, used/available/total slot count, and used or available or total capacity. Two calculated columns show the % utilization of slots and library capacity. The report provides a rich selection of

646

Reporting in OpsCenter About Report Templates descriptions

filters enabling users with a diverse tape library environment to zoom in on any segment of their tape library population. Note: The Library Summary report might display some negative values. These negative values are a result of negative slot counts. If the user added -1 NetBackup is unable to connect to the media. If the slot count is 0 NetBackup only calculates data for TLD and TLD8 media leading to negative values in the report. The user must enter the media slot count from Settings > Configuration > Tape Library. See Modifying tape library information in OpsCenter on page 316.

Library Capacity Forecast report

This report provides a capacity forecast of Tape Libraries. A libraries capacity is calculated by multiplying Slot Count by Slot Capacity. Slot capacity is the capacity of the tape in the slot. As no standard exists for measuring library capacity, the report enables several methods by which an individual tapes capacity is determined. These consist of using the maximum, the minimum and the average size of full tapes to determine tape capacity. Additionally, user-defined capacity for tape types is available in the report parameter selection UI. The report extrapolates out the trend line through the forecast period using classic linear regression and also plots the libraries capacity. At the date in which the library capacity line intersects the capacity forecast line is when the libraries capacity is reached.

Drive Throughput report

This report shows the speed (KB/Sec) at which data backups flows through tape drives. The report uses the heat map concept and depicts ranges of speeds (slow to fast) through configurable shades of green. Reports are based on either Hour-Of-Day or Day-of-Week. Advanced averaging logic is used to determine the throughput values for each cell in the report. The averaging is done at an image fragment level ensuring granularity and precision in calculations. The reports can be aggregated and filtered at the Tape Library, Media Server, Drive Type, Logical Drive, and Physical Drive levels. The sort options allow for intuitive presentation of voluminous data. These reports are important sources of information for performance analysis and capacity planning activities.

Drive Utilization report

This report shows the utilization (0 100%) of tape drives. The report uses the heat map concept and depicts ranges of utilization (low to high) through configurable shades of blue for example. Reports are based on either Hour-Of-Day

Reporting in OpsCenter About Report Templates descriptions

647

or Day-of- Week. Advanced logic is used to determine the utilization values for each cell in the report. Utilization is calculated off a per minute basis ensuring precision in calculations versus traditional methods of periodic polling of the devices. The reports can be aggregated and filtered at the Tape Library, Media Server, Drive Type, Logical Drive, and Physical Drive levels. The sort options allow for intuitive presentation of voluminous data. These reports are important sources of information for performance analysis and capacity planning activities.

SAN client jobs report

This report shows all the jobs for selected Fiber Transport (FT) media servers and selected SAN clients. The report answers the following questions and provides the following information:

Did the job run on a LAN or an FT pipe? Are two different clients backed up by a single media server, thus reducing the throughput? A list of all the FT media servers A list of all the SAN clients.

About Media reports in OpsCenter

This section describes media reports.
Media State report Available Media report Drives in Use report Full Media Capacity report Media Summary by Media Server report See Media State report on page 648. See Available Media report on page 648. See Drives in Use report on page 648. See Full Media Capacity report on page 648. See About Media Summary by Media Server report on page 648. See Media Utilization report on page 649. See Tape Count report on page 649. See Tapes Expiring in Future report on page 650. See Tapes Expiring Now report on page 650. See Vault Media Usage report on page 650.

Media Utilization report Tape Count report Tapes Expiring in Future report

TapesExpiring Now report

Vault Media Usage report

648

Reporting in OpsCenter About Report Templates descriptions

Media Expiration Schedule report

See Media Expiration Schedule report on page 651.

Media State report

This report displays the media status and count (per media type) for each master server and media server combination. Media state can be frozen, active, off-site, and so on.

Available Media report

This report lists the media that is available for use by NetBackup for each master server that is selected. The report table provides information, such as, media server, media status, robot type, volume group and pool, and the time assigned.

Drives in Use report

This report shows the drive usage for the selected server. The report table provides details for the drive, for example, drive name and type, robot number and type, and assigned host.

Full Media Capacity report

This report shows the average amount of protected data (in kilobytes) on a tape for each master server and media type. These are the tapes that NetBackup marked as full. The bar chart depicts the amount of data (in kilobytes) per media type. The report table is organized by server, media type and count, and shows the size and number of images on the tape.

About Media Summary by Media Server report

For each media server, this report provides the number of tapes and images, the last written date, and amount of data on the tapes. The name of the media server is also a drilldown link to a detailed report for media.

Reporting in OpsCenter About Report Templates descriptions

649

Media summary by media status for a media server report

This drilldown report from the Media Server column provides a media status summary for a selected media server. This report displays media status, number of tapes and images, the last written date, and amount of data on tapes. This drilldown report uses the run time parameters that are passed from the main report.

Media details of media status for a media server report

This drilldown report from the Media Status column provides media details for the selected media server and selected media status. Media status can be Active, Frozen, Full, Invalid, or Suspended. This drilldown report uses the run time parameters that are passed from the main report. The report displays media ID, type, volume pool, last written date, expiration date, number of images, and the amount of data on tape.

Media Utilization report

The stacked bar chart in this report shows the number of media in use for a server per date. The segments in the bars show assigned, unassigned, frozen, full, off-site, or suspended media states. Tool tips in the chart show the count for each media state. The data for this report is only calculated once in a day. So the report shows the summary till the previous date. The data for today reflects in the report that you generate tomorrow. The table in the report is organized by date and server, and shows counts for each media state.

Tape Count report

This report shows tape count for the following Report On parameters:

Backup Media Retention Level Tape Type Volume Pool Name

In Veritas Backup Reporter (VBR), there was a separate report for each of these parameters. In OpsCenter, the three reports are merged into one report. The Tape Count report is available in the Distribution view.

650

Reporting in OpsCenter About Report Templates descriptions

Tapes Expiring in Future report

This report shows the number of media that expire at each day in the upcoming seven days. This time frame can be changed to show more in to the future. The report is helpful in determining if a large quantity of media may become free in the future which could justify delaying the purchase of more media. Note: The filter Backup Media Role applied to the Tape Expiring Now report does not return any data.

Tapes Expiring Now report

This report lists the media that are about to expire. The Volume Pool Name , Media ID, and Media Barcode that are listed make it easy to locate the media. The default time frame when the report is clicked will show what is expiring in the next 24 hours. That time frame can be changed to show media expiring in the next week, month, or any future time window desirable.

Vault Media Usage report

This report shows off-site media trends for selected vaults and current off-site media count. The report consists of two component reports, a bar chart and a table. This report helps understand your off-site media trends. Questions like the following are answered by this report:

How does the off-site media count vary for each vault? What are the details of the current off-site media ?

The bar chart shows the weekly trend of off-site media counts for selected vaults. While running the report you select the vaults for which you want to run this report. The report shows a weekly line trend for selected vault. This chart is a good indication of how the off-site media count varies over the period of time. You can compare the media counts of different vaults to see which vault is consuming more media and how it varies. The report table provides the details of vaulted media for the selected vaults. When you run the report you specify the vault names. The report provides important media details like media ID, off-site slot number, container ID, expiration date, bar code, and so on.

Reporting in OpsCenter About Report Templates descriptions

651

Media Expiration Schedule report

This report gives graphical representation of the expiration schedule for media. The report predicts the availability of media based on the expiration date of the media. Using this report you can determine what media will be available for reuse. The stacked bars represent the number of media of a specific type that are expired on a particular day. Different colors are used in the bars for the different media types. Tool tips for the bar segments provide the media type and count of the media that is available on that day.

About Performance reports in OpsCenter

This section describes performance reports.
Storage Unit Usage report Master Server Job Throughput report See Storage Unit Usage report on page 651. See Master Server Job Throughput report on page 652. See Media Server Job Throughput report on page 653. See Disk Usage report on page 653.

Media Server Job Throughput

Disk Usage report

Storage Unit Usage report

This report shows storage unit usage for a selected master server and time frame. The first column of each row of the report table lists a storage unit. The storage unit name is also a drilldown link to a detailed report. The media server name in the second column is also a drilldown link. The rest of the row provides details such as total number of jobs, total volume processed (KB), average throughput (KB/sec), duration of activity and percentage of utilization in terms of duration.
Storage unit throughput report This drilldown report from the Storage Unit column shows the data transfer rate (throughput) of the selected storage unit. This drilldown report uses the run time parameters that are passed from the main report.

652

Reporting in OpsCenter About Report Templates descriptions

Storage unit usage details for media server report

This drilldown report from the Media Server Name column shows the usage details for all of the storage units of the selected media server. This drilldown report uses the run time parameters that are passed from the main report. The Storage unit column of the report table is a link to a drilldown throughput report. The rest of the cells indicate whether the storage unit was in use or not during the time slot.

Master Server Job Throughput report

This report provides a tool to compare performance of various master servers. The pie chart displays the breakdown of jobs that are run across the selected master servers. A drilldown detail link from each server pie slice for job details is provided. The table of this report displays throughput and job success information for each server in the selected server context. It shows job count and job success rate, and enables you to compare throughputs of different servers to identify any servers that are performing poorly. Drilldown links for the server name, number of total and successful jobs columns are also provided.
Total jobs of a server report This drilldown report from the pie chart or Number of Total Jobs column lists the details for all jobs for a selected server. The report details include details like job type and status, policy and schedule names, and start time. This drilldown report uses the run time parameters that are passed from the main report. Job details for client and master server This drill-down report from the client name report column provides details for a given client, job type, and job status. The report details include exit status, start time, duration in seconds, volume in KB, and throughput. This drilldown report uses the run time parameters that are passed from the main report.

Reporting in OpsCenter About Report Templates descriptions

653

Successful jobs of a server report

This drilldown report from the Number of Successful Jobs column shows details for successful jobs for a given server. The report provides details like job type, policy and schedule names, volume, and file counts. This drilldown report uses the run time parameters that are passed from the main report.

Media Server Job Throughput report

This report provides details of data that is backed up by NetBackup media servers and shows server throughput. The report is a useful tool to compare performance of the media servers that are present in your NetBackup environment. The pie chart provides a breakdown of the volume of data that is processed for each media server. A drilldown detail link for throughput details is provided from each volume pie slice.
Job details for client and media server This drilldown report from the client name report column provides details for a given client, job type, job status, and media server. The report details include job ID, job type, exit status, start time, and duration in seconds. This drilldown report uses the run time parameters that are passed from the parent report. Media server throughput for media server report You can use this drill-down report from the Throughput (KB/sec) column to see the variation of throughput per day. The throughput is represented by a bar for each day of the reporting period. This drill-down report uses the run time parameters that are passed from the main report.

Disk Usage report

This report shows disk usage for the selected server and time frame. The table in the report provides details such as total number of jobs, total volume processed (KB), average throughput (KB/sec), duration of activity, and percentage utilization in terms of duration. The Disk and Media Server Name columns of the table contain drilldown links to detailed throughput and disk usage reports.

654

Reporting in OpsCenter About Report Templates descriptions

Disk throughput for storage unit report This drilldown report from the Disk column shows the data transfer rate (throughput) for a disk storage unit for the selected server or server groups. This drilldown report uses the run time parameters that are passed from the main report. Disk usage details for media server report This drilldown report from the Media server Name column shows the usage details for all the disk storage units for the selected media server. This drilldown report uses the run time parameters that are passed from the main report. The Disk cell in each row of the report table is a link to a drill-down report. The rest of the cells indicate whether the disk was in use or not during the time slot.

About Policy reports in OpsCenter

This section describes policy reports.
Top 10 Policies Using Most Server Space report Job Success Rate by Policy Type report See Top 10 Policies Using Most Server Space report on page 654. See Job Success Rate by Policy Type report on page 655. See Policy Change report on page 656. See Policy Summary Dashboard report on page 656.

Policy Change report Policy Summary Dashboard report

Top 10 Policies Using Most Server Space report

This report displays the 10 policies that have backed up the most data in your NetBackup environment. Since the report is based on the server context selected it is possible to get information for each individual managed server or for a group of servers. Drilldown links from the bar chart (tool tips) and the table in the report provide details for the selected policy. The tool tip also shows the volume of data in MBs. The report table includes information, such as, number of jobs and files, and volume of data.

Reporting in OpsCenter About Report Templates descriptions

655

A drilldown report is available from the main report. This drilldown report from the Policy Name column and the colored bars in the chart provides details about all jobs for a selected policy name. This drilldown report uses the run time parameters that are passed from the main report. The table includes information, such as, job type, exit status, client name, and volume in KB.

Job Success Rate by Policy Type report

This report provides a quick view of the status of jobs by policy type. The report shows the job success rate for clients, server, and job policy type. The bar chart shows the count of successful, partially successful, and failed jobs per policy type. The tool tips in the colored bars provide job counts and also are drilldown links to view the details for the policy. The table in the report displays job information, such as, client name, policy type, and the success rate. Note: This report may not show appropriate data for duplication jobs that are associated with SLP policy. This issue occurs because the duplication jobs do not have a policy type. The job batches duplication of images that are created from possibly different policies and policy types. The duplication job itself has an internal policy that is created but this internal policy does not have the policy type set because this is not a backup job.
Job details for policy type report This drilldown report from the Policy Type column and the colored bars in the chart provides details about all jobs for a selected policy type. This drilldown report uses the run time parameters that are passed from the main report. The table includes information, such as, exit status, client name, volume in KB, and count of files.

656

Reporting in OpsCenter About Report Templates descriptions

Successful, partially successful, and There are three drilldown reports from the failed job details for policy type report Number of Successful Jobs, Number of Partially Successful Jobs, or Number of Failed Jobs columns. The job exit status is used as a filter for the reports. These reports are similar and provide details for all jobs for a selected client and policy type. This drilldown report uses the run time parameters that are passed from the main report. The table in this report provides details like, policy and schedule name, start and end times, and duration for the job. The table for failed jobs also includes a column for the job exit status.

Policy Change report

This report shows a count of the changes that were made to job policies in a given time frame for the selected servers. The pie chart shows the number of policy changes (a policy can change multiple times) for each master server. (Each different server appears in a different color in the chart.) Tool tips in the chart provide a count of the changes. The table in the report displays the count of changes that were made to each policy for each server.

Policy Summary Dashboard report

This report acts as a dashboard of activities that are summarized by your policies. It gives an overview of activities and can be used as a tool to troubleshoot and manage by exception using the drilldown links to other detail reports. It provides answers for some of the following questions for each policy:

What is the total number of jobs? How many jobs were successful? How many jobs were partially successful? How many jobs failed?

The table in this report shows information per policy like policy name and type, job volume in MB, job count, and counts for job exit status. You can also drill down from the job exit status counts in the columns and view individual policy details based on exit status and job policy and type.

Reporting in OpsCenter About Report Templates descriptions

657

There are drilldown reports available from the Total Jobs, Successful Jobs, Partial Jobs, or Failed Jobs columns of the main report. These drilldown reports provide an overview of all jobs for the selected policy name, server, and time frame based on the job exit status. These drilldown reports use the run time parameters that are passed from the main report. The table provides details like schedule name, start times, and duration of the job.

About Restore reports in OpsCenter

This section describes restore job reports. These reports are applicable only for NetBackup.
Restore Job Summary by Job Count report See Restore Job Summary by Job Count report on page 657. See Restore Job Summary by Volume Restored report on page 657. See Restore Job Details report on page 657.

Restore Job Summary by Volume Restored report Restore Job Details report

Restore Job Summary by Job Count report

This report is a graphical summary of the number of restore jobs that were run for the selected time frame.

Restore Job Summary by Volume Restored report

This report shows the restore job count by volumes.

Restore Job Details report

This report provides details of restore jobs. The report lists all completed restore jobs for the selected time frame. The table in the report is organized by job ID, master server name, and client.

About Storage Lifecycle Policy reports

The Storage Lifecycle Policy reports in OpsCenter help you gain an end-to-end visibility across destinations in a storage lifecycle policy. With NetBackup 7.1, you can duplicate to remote master servers and thus specify a different master server as a storage destination in an SLP. The SLP reports in OpsCenter show an

658

Reporting in OpsCenter About Report Templates descriptions

end-to-end view of the SLP process that includes backup to import of duplicated image into different NetBackup domains. The SLP reports help you to verify if each step in the SLP is executed and identify the possible bottlenecks. The Storage Lifecycle Policy reports in OpsCenter help you find answers to the following questions:

Is the SLP performing according to schedule? Have the 2nd, 3rd Copies been made? Does the original image still exist? Am I at a risk of data loss? A copy at a certain phase is about to expire and the subsequent phases copy has not been made. What is my backlog? Is it getting steadily worse?

Review the following points about SLP reports:

The SLP reports are applicable only to NetBackup. The SLP reports can be run only for 7.1 or higher master servers. If you upgrade from 7.0 (or 7.0.1) to a 7.1 master server, the SLP reports also show the images for 7.0 or 7.0.1 master servers. If you upgrade NetBackup from 7.0 or 7.0.1 to 7.1 and the SLP definition contains multiple backup operations, then the first copy is marked as "Backup" and the remaining are marked as "Duplication". For example, if you created an SLP that contains four destinations where two destinations are for backup and two are for duplication, then image copy data marks the first copy as Backup and remaining for Duplication. The data that is shown in the SLP reports is collected from the NetBackup catalog and the SLP worklist by NBSL. Once the initial data collection is complete, the updated data is collected from the NetBackup catalog in every 15 minutes and from the SLP worklist in every 10 minutes. The SLP worklist is located in the EMM and contains metadata like how many copies need to be created, where they need to be created, when they are completed etc. The data that is displayed in the SLP reports is based on the image data that exists in the SLP worklist and the NetBackup catalog. The effects of deduplication, compression, or optimized deduplication on image or copy size are not considered in the SLP reports. By default, data for SLP reports is purged from the OpsCenter database after 90 days. You can also customize the purge interval for SLP images from Settings > Configuration > Data Purge. In general, the copy data in the SLP reports (like Copies Completed column) is based on the data that is collected from the SLP worklist. EMM creates the SLP worklist once a backup is complete. OpsCenter collects this data in every 10 minutes and shows it in the SLP reports. Depending on when the SLP worklist

Reporting in OpsCenter About Report Templates descriptions

659

is created and also the OpsCenter data collection cycle, the OpsCenter reports show details for the copy data.

The timeframe filter for all SLP reports is based on the time when the primary backup image (and not an image copy) was created. For example, if you view the SLP Status by Image Copy report between 7'th May 1:00 P.M. to 8'th May 1:00 P.M., then the copies that got created for an SLP after 8'th May 1:00 P.M. may be displayed. These copies may be displayed as the timeframe filter is based on the time when the primary backup image was created and not on the copy creation time. SLP reports do not consider non-SLP based duplications. Creating custom reports for SLPs is not supported.

The following are two high-level SLP reports:

SLP Status report See About the SLP Status report on page 660. See About the SLP Backlog report on page 665.

SLP Backlog report

Before using the SLP reports, you must understand the SLP concept and how duplication to remote master servers works in NetBackup. See About SLP and duplication to remote master servers on page 659.

About SLP and duplication to remote master servers

This section gives a brief overview about SLP and also duplicating to remote master servers in NetBackup. A Storage Lifecycle Policy (SLP) is a storage plan that specifies where data will be stored and for how long. The SLP determines where the backup image is initially written and where it is subsequently duplicated. With NetBackup 7.1, you can also duplicate backup image or duplicate copies from one storage domain to another for business continuity planning purposes. This means that you can now copy backup images from one master server to another master server, and also specify a different master server as a storage destination in an SLP. The SLP and duplication to remote master functionality in NetBackup allows you to move data to tiers of storage on different master servers commensurate with the value of the data as it ages. More information about SLP and duplication to remote master functionality is available in the Symantec NetBackup Administrators Guide.

660

Reporting in OpsCenter About Report Templates descriptions

About the SLP Status report

The SLP Status report provides a summary of lifecycle policies that are associated with a master server. The SLP Status report is a tabular report that lets you know the current progress of SLPs in the selected timeframe for each master server that is added to the OpsCenter console. The SLP status report gives a quick summary of the SLP activity and lets you identify the SLPs that are incomplete. You can see if all your duplications (copies) are complete or not. By clicking the links in the SLP Status report, you can drill down to more detailed reports. You can use the drill-down reports to focus on SLPs, images, or the image copies that are incomplete. You can also view SLP status for each destination and also for each SLP. From the SLP Status report, you can drill down to the following reports:
SLP Status by SLP report See About the SLP Status by SLP report on page 666. From the SLP Status by SLP report, you can drill down to the following reports: SLP Status by Destinations report See About the SLP Status by Destinations report on page 684. SLP Duplication Progress report See About the SLP Duplication Progress report on page 688.

SLP Status by Client report SLP Status by Image report SLP Status by Image Copy report

See About the SLP Status by Client report on page 670. See About the SLP Status by Image report on page 675. See About the SLP Status by Image Copy report on page 680.

The SLP Status report comprises of the following columns:

Master Server (where the SLP lives) Name of the master server (link) where the SLP runs. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The NetBackup master server must be of version 7.1 and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. Click on the master server (link) to see the drilldown report named SLP Status by SLP.

Reporting in OpsCenter About Report Templates descriptions

661

Oldest Unfinished Image

This column tells you about the oldest image that is SLP-incomplete for the selected master server. This column represents the image end time (and date). The data from this column helps you to identify the possible bottlenecks in the SLP process. This column is mandatory and cannot be removed when you edit the report.

Total Clients

Number of the unique clients that are backed up by the SLP for the selected master server. Note that if the same client is backed up twice or thrice by the SLP, the client is counted only once. Click the number (link) to view the SLP Status by Client report. This column is mandatory and cannot be removed when you edit the report.

Total Existing Images

Total number of the images that are present in the OpsCenter database for SLPs on the selected master server (includes both SLP-complete images and SLP-incomplete images). Click the number (link) to view the SLP Status by Image report for the specific master server. This report displays details of images in the OpsCenter database that are associated with the SLPs on the selected master server. This column is mandatory and cannot be removed when you edit the report.

Images % SLP Complete

Percentage of images in the OpsCenter database that are SLP-complete for the selected master server. This column is calculated using data from the following columns of the SLP Status report:

Images SLP Complete Total Existing Images

The contents of Images % SLP Complete column is calculated by using the following formula: Images SLP Complete / Total Existing Images * 100 This column is mandatory and cannot be removed when you edit the report.

662

Reporting in OpsCenter About Report Templates descriptions

Images SLP Complete

Number of images in the OpsCenter database that are SLP-complete for the specific SLP on the selected master server. You can remove this column when you edit the report. Click the number (link) to view the SLP Status by Image report. A filtered view of the report appears that displays details of images in the OpsCenter database that are SLP-complete for the specific SLP.

Images Not SLP Complete

Number of images in the OpsCenter database that are SLP-incomplete for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image report. A filtered view of the report appears that displays details of images in the OpsCenter database that are SLP-incomplete.

Total Expected Copies

Total number of image copies in the OpsCenter database for the specific SLP on the selected master server (includes both complete copies and incomplete copies). This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image Copy report.

% Copy Complete

Percentage of completed copies in the OpsCenter database for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by using data from the following columns of the SLP Status By SLP report:

Copies Completed Total Copies

The contents of % Copy Complete column is calculated by using the following formula: Copies Completed / Total Copies * 100

Reporting in OpsCenter About Report Templates descriptions

663

Copies Completed

Number of the completed copies that are present in the OpsCenter database for SLPs on the selected master server. Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are complete for the selected master server. You can remove this column when you edit the report.

Copies Not Complete

Number of incomplete copies in the OpsCenter database for SLPs on a selected master server. This column is calculated using the following formula: Copies Not Complete = Total Copies Copies Completed Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for image copies in the OpsCenter database that are incomplete for the selected master server. This column is mandatory and cannot be removed when you edit the report.

Total Expected Size - all copies (MB)

Expected aggregate size of all copies for SLPs on the selected master server that are present in the OpsCenter database. This column is mandatory and cannot be removed when you edit the report. The Total Expected Size for all copies is calculated by using the following formula: Total Expected Size for all copies = (Number of copies) * (backup copy size)

Note: The total expected size for all copies is a front-end

size and is derived from the number of copies multiplied by the size of backup copy. The effects of deduplication, compression, or optimized deduplication on the Total Expected Size all copies are not considered in the SLP reports.

664

Reporting in OpsCenter About Report Templates descriptions

Completed Copy Size (%)

Percentage of completed copy size for the selected master server. This column is mandatory and cannot be removed when you edit the report. The Completed Copy Size (%) for the specific master server is calculated using data from the following columns of the SLP Status report:

Completed Copy Size Total Expected Size all copies

The contents of Completed Copy Size (%) column is calculated for each master server by using the following formula: Completed Copy Size / Total Expected Size all copies * 100 Completed Copy Size (MB) Aggregate size of all the completed copies in the OpsCenter database for the selected master server. You can remove this column when you edit the report. Note: The Completed Copy Size is a front-end size. The effects of deduplication, compression, or optimized deduplication on completed copy size are not considered in the SLP reports. Aggregate size of all remaining copies that are to be created for the selected master server. This column is mandatory and cannot be removed when you edit the report. The Remaining Copy Size (MB) for a specific master server is calculated in the following manner: (Remaining Copy Count) x (Size of Backup Copy1)

Remaining Copy Size (MB)

Note: The remaining copy size is a front-end size and is

derived from the number of remaining copies multiplied by the size of backup copy 1. The effects of deduplication, compression, or optimized deduplication on remaining copy size are not considered in the SLP reports.

You can use filters to view specific data in the SLP Status report. The following filters are available when you edit the SLP Status report:
Views Master Server Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers.

Reporting in OpsCenter About Report Templates descriptions

665

About the SLP Backlog report

The SLP Backlog report lets you monitor the overall SLP backlog in a glance. This report shows the trend of images created vs. the images which are SLP incomplete in a line chart format. This report illustrates what the SLP backlog looks like against the image creation volume for the selected timeframe and the selected SLPs. By comparing the line charts in this report, you can understand the rate at which copies are created vs. the rate at which images requiring copies are created. This report provides you with empirical evidence on how efficiently the SLP performs and visibility into its capacity (i.e. at what point does the outflow begin to fall steadily behind). Data for the SLP Backlog report is collected from the OpsCenter database at midnight (12:00 A.M. by the OpsCenter Server clock). The data collection for the SLP Backlog report occurs after every 24 hours. This report is available in both graphical (chart) and tabular formats. To view the report details in a tabular format, click the link Show Chart as Table at the bottom of the report. You can edit the report to view specific data in the report. You can also save this report. Note that when you save the SLP Backlog report and run the saved report after some time, the report displays current data. You can export or email this report for reference. Note that the data that is shown in the SLP Backlog report (images that are created and unfinished images) is in GB by default. You can edit the report and change the units to KB, MB, or TB. The default timeframe for the SLP Backlog report is last two weeks. While editing the SLP Backlog report, you can group the timeframe for which you want to see data. However, the time frame grouping for the SLP Backlog report is supported for the following intervals only:

one day one week one month

The SLP Backlog report does not support any other time frame grouping (like two days, three months, 1 minute, or four weeks). You can use filters to view specific data in the SLP Backlog report. The following filters are available when you edit the SLP Backlog report:
Views Master Server Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers.

666

Reporting in OpsCenter About Report Templates descriptions

Storage Lifecycle Policy

Select one or more SLPs to see data for the selected SLPs.

About the SLP Status by SLP report

You can view the SLP status by SLP report when you click the master server (link) in the SLP report. It provides detailed information on the status of each SLP that is configured on the selected master server. The SLP status by SLP report lets you monitor the progress of each SLP and also quickly identify the possible bottlenecks. The SLP Status by SLP report comprises of the following columns:
Master Server (where the SLP lives) Name of the master server where the SLP runs. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The NetBackup master server must be of version 7.1 and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. SLP Name Name of the SLP (link) that is configured on the master server. This column is mandatory and cannot be removed when you edit the report. Click the name (link) to view the SLP Status by Destinations report. SLP Version Version (link) that is associated with the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. Click the version (link) to view the SLP Duplication Progress report. Oldest Unfinished Image The oldest image that is not SLP-complete for the specific SLP on the selected master server. This column represents the image end time (and date). This data helps you to identify the possible bottlenecks for the specific SLP. This column is mandatory and cannot be removed when you edit the report.

Reporting in OpsCenter About Report Templates descriptions

667

TotaI Clients

Number of unique clients (link) that are backed up by the specific SLP. Note that if the same client is backed up twice or thrice by the SLP, the client is counted only once. This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Client report.

Total Existing Images

The total number of images that are present in the OpsCenter database for the specific SLP on the selected master server. This includes both SLP-complete images and SLP-incomplete images. This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image report for the specific SLP on the selected master server. This report displays details of images in the OpsCenter database that are associated with the SLPs on the selected master server.

Images % SLP Complete

Percentage of images in the OpsCenter database that are SLP-complete for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated using data from the following columns of the SLP Status by SLP report:

Images SLP Complete Total Existing Images

The contents of Images % SLP Complete column is calculated by using the following formula: Images SLP Complete / Total Existing Images * 100 Images SLP Complete Number of images in the OpsCenter database that are SLP-complete for the specific SLP on the selected master server. You can remove this column when you edit the report. Click the number (link) to view the SLP Status by Image report. A filtered view of the report appears that displays details of images in the OpsCenter database that are SLP-complete for the specific SLP.

668

Reporting in OpsCenter About Report Templates descriptions

Images Not SLP Complete

Number of images in the OpsCenter database that are SLP-incomplete for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image report. A filtered view of the report appears that displays details of images in the OpsCenter database that are SLP-incomplete.

Total Expected Copies

Total number of image copies in the OpsCenter database for the specific SLP on the selected master server (includes both complete copies and incomplete copies). This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image Copy report.

% Copy Complete

Percentage of completed copies in the OpsCenter database for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by using data from the following columns of the SLP Status By SLP report:

Copies Completed Total Copies

The contents of % Copy Complete column is calculated by using the following formula: Copies Completed / Total Copies * 100 Copies Completed The number of completed copies that are present in the OpsCenter database for the specific SLP on the selected master server. You can remove this column when you edit the report. Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are complete for the selected master server.

Reporting in OpsCenter About Report Templates descriptions

669

Copies Not Complete

Shows the number of incomplete copies in the OpsCenter database for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by using the following formula: Copies Not Complete = Total Copies Copies Completed Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are incomplete for the selected SLP.

Total Expected Size - all copies (MB)

Expected aggregate size of all copies for the selected SLP that are present in the OpsCenter database. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by using the following formula: Total Expected Size for all copies = (Number of copies for the specific SLP) * (backup copy size for the specific SLP)

Note: The total expected size for all copies is a front-end

size and is derived from the number of copies multiplied by the size of backup copy. The effects of deduplication, compression, or optimized deduplication on the Total Expected Size all copies are not considered in the SLP reports. Completed Copy Size (%) Percentage of completed copy size for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated from the following columns of the SLP Status By SLP report:

Completed Copy Size Total Expected Size all copies

The contents of Completed Copy Size (%) column is calculated by using the following formula: Completed Copy Size / Total Expected Size all copies * 100

670

Reporting in OpsCenter About Report Templates descriptions

Completed Copy Size (MB)

Aggregate size of all the completed copies in the OpsCenter database for the specific SLP on the selected master server. You can remove this column when you edit the report.

Note: The Completed Copy Size is a front-end size. The

effects of deduplication, compression, or optimized deduplication on completed copy size are not considered in the SLP reports. Remaining Copy Size (MB) Aggregate size of all remaining copies that are to be created for the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated in the following manner: (Remaining Copy Count for the specific SLP) x (Size of backup copy for the specific SLP)

Note: The remaining copy size is a front-end size and is

derived from the number of remaining copies multiplied by the size of backup copy 1. The effects of deduplication, compression, or optimized deduplication on remaining copy size are not considered in the SLP reports.

You can use filters to view specific data in the SLP Status by SLP report. The following filters are available when you edit the SLP Status by SLP report:
Views Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers. Select one or more SLPs to see data for the selected SLPs.

Master Server

Storage Lifecycle Policy

The default timeframe for this report is based on what timeframe is selected for the top-level report.

About the SLP Status by Client report

The SLP Status by Client report is available as a drill-down report from the SLP Status and SLP Status by SLP report. You can view the SLP status by Client report when you click the links in the Total Clients column in the following reports:

SLP Status

Reporting in OpsCenter About Report Templates descriptions

671

SLP Status by SLP (a filtered view of the SLP status by Client report is shown)

The SLP Status by Client report lets you monitor the SLP progress for each client that is associated with the SLP. This report helps you to know details about the SLPs that protect the clients. This report also provides details about origin master server (master server where the data is backed up) and the master server where the SLP is running currently. The origin master server and master server where the SLP is running currently may be different when you duplicate to remote master server. The SLP Status by Client report comprises of the following columns:
Master Server (where the SLP lives) Name of the master server where the SLP that is associated with the client exists. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The NetBackup master server must be of version 7.1 and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. SLP Name Name of the SLP that is associated with the selected master server and client. This column is mandatory and cannot be removed when you edit the report. Version that is associated with the specific SLP. This column is mandatory and cannot be removed when you edit the report. Client name (link) that is backed up by the specific SLP on the selected master server. This column is mandatory and cannot be removed when you edit the report. Click the client name (link) to view the SLP Status by Image report. The SLP Status by Image report is filtered for the specific client and the specific SLP. Origin Master Server (created the image) Origin Master Server is where the primary backup copy resides. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The Origin Master Server must be a NetBackup 7.1 master server and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report.

SLP Version

Client Name

672

Reporting in OpsCenter About Report Templates descriptions

Oldest Unfinished Image

This column tells you about the oldest image that is not SLP-complete for the selected master server, SLP, and client. This column represents the image end time (and date). This data helps you to identify the possible bottlenecks for the specific SLP. This column is mandatory and cannot be removed when you edit the report.

Total Existing Images

The total number of images that are present in the OpsCenter database for the specific SLP and client on the selected master server. This includes both SLP-complete images and SLP-incomplete images. This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image report for the specific SLP on the selected master server. This report displays details of images in the OpsCenter database that are associated with the SLPs and client on the selected master server.

Images % SLP Complete

Percentage of images in the OpsCenter database that are SLP-complete for the specific SLP and client on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this report is calculated from the following columns of the SLP Status by Client report:

Images SLP Complete Total Existing Images

The data in the Images % SLP Complete column is calculated by using the following formula: Images SLP Complete / Total Existing Images * 100 Images SLP Complete Number of images in the OpsCenter database that are SLP-complete for the specific SLP and client on the selected master server. You can remove this column when you edit the report. Click the number (link) to view the SLP Status by Image report. A filtered view of the report appears that displays details of images in the OpsCenter database that are SLP-complete for the specific SLP and client.

Reporting in OpsCenter About Report Templates descriptions

673

Images Not SLP Complete

Number of images in the OpsCenter database that are SLP-incomplete for the specific SLP and client on the selected master server. This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image report. A filtered view of the report appears that displays details of images in the OpsCenter database that are SLP-incomplete.

Total Copies

Total number of copies in the OpsCenter database for the specific SLP and client on the selected master server (includes both complete copies and incomplete copies). This column is mandatory and cannot be removed when you edit the report. Click the number (link) to view the SLP Status by Image Copy report.

% Copy Complete

Percentage of completed copies in the OpsCenter database for the specific SLP and client on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated from the following columns of the SLP Status by Client report:

Copies Completed Total Copies

The contents of % Copies Complete column is calculated by using the following formula: Copies Completed / Total Copies * 100 Copies Completed The number of completed copies that are present in the OpsCenter database for the specific SLP and client on the selected master server. You can remove this column when you edit the report. Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are complete for the selected master server.

674

Reporting in OpsCenter About Report Templates descriptions

Copies Not Complete

Shows the number of incomplete copies in the OpsCenter database for the specific SLP and client on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by the following formula: Copies not Complete = Total Copies Copies Completed Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are incomplete for the selected SLP.

Total Expected Size - all copies (MB)

Expected aggregate size of all copies for the selected SLP and client that are present in the OpsCenter database. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by the following formula: Total Expected Size for all copies = (Number of copies) * (backup copy size)

Note: The total expected size for all copies is a front-end

size and is derived from the number of copies multiplied by the size of backup copy. The effects of deduplication, compression, or optimized deduplication on the Total Expected Size all copies are not considered in the SLP reports. Completed Copy Size (%) Percentage of completed copy size for the specific SLP and client on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated from the following columns of the SLP Status by Client report:

Completed Copy Size Total Expected Size all copies

The contents of Completed Copy Size (%) column is calculated by using the following formula: Completed Copy Size / Total Expected Size all copies * 100

Reporting in OpsCenter About Report Templates descriptions

675

Completed Copy Size (MB)

Aggregate size of all the completed copies in the OpsCenter database for the specific SLP and client on the selected master server. You can remove this column when you edit the report.

Note: The Completed Copy Size is a front-end size. The

effects of deduplication, compression, or optimized deduplication on completed copy size are not considered in the SLP reports. Remaining Copy Size (MB) Aggregate size of all remaining copies that are to be created for the specific SLP and client on the selected master server. This column is mandatory and cannot be removed when you edit the report. The column content is calculated in the following manner: (Remaining Copy Count) x (Size of Backup Copy1)

Note: The remaining copy size is a front-end size and is

derived from the number of remaining copies multiplied by the size of backup copy 1. The effects of deduplication, compression, or optimized deduplication on remaining copy size are not considered in the SLP reports.

You can use filters to view specific data in the SLP Status by Client report. The following filters are available when you edit the SLP Status by Client report:
Views Master Server Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers. Select one or more SLPs to see data for the selected SLPs. Select one or more clients to see data for the selected clients.

Storage Lifecycle Policy Client

The default timeframe for this report is based on what timeframe is selected for top-level report.

About the SLP Status by Image report

The SLP Status by Image report is available as a drill-down report from the SLP Status, SLP Status by SLP, and SLP Status by Client report. You can view the SLP Status by Image report when you click the links in the following columns:

Total Existing Images Images SLP Complete (filtered view of the SLP Status by Image report is shown)

676

Reporting in OpsCenter About Report Templates descriptions

Images Not SLP Complete (filtered view of the SLP Status by Image report is shown)

The SLP Status by Image report lets you monitor the lifecycle for the images that are associated with the SLP. This report helps you to know which images are complete and incomplete for a specific SLP and identify bottlenecks in the SLP process. This report gives an idea of how a specific image is duplicated across master servers and also provides specific details about the image like backup time, SLP completion time, copies associated with each image and its status etc. The SLP status by Image report can help you to identify the image IDs that are not SLP-complete. The SLP Status by Image report comprises of the following columns:
Master Server (where the SLP lives) Name of the master server where the SLP runs. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The NetBackup master server must be of version 7.1 and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. SLP Name Name of the SLP that is associated with the selected master server and image. This column is mandatory and cannot be removed when you edit the report. SLP Version Version (link) that is associated with the specific SLP. This column is mandatory and cannot be removed when you edit the report. Click the version (link) to view the SLP Duplication Progress report. Policy that is associated with the SLP. This column is mandatory and cannot be removed when you edit the report. Schedule that is associated with the policy. You can remove this column when you edit the report. Client name that is backed up by the SLP for the selected master server. This column is mandatory and cannot be removed when you edit the report.

Policy Name

Schedule Name

Client Name

Reporting in OpsCenter About Report Templates descriptions

677

Origin Master Server (created the image)

Origin Master Server is where the primary backup copy resides. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The origin master server and master server where the SLP lives (or is running currently) may be different if you duplicate to a remote master server. The Origin Master Server must be a NetBackup 7.1 master server and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report.

Image ID

Image ID (link) associated with the image. The Image ID is unique for each image. Click the image ID (link) to view the SLP Status by Image Copy report. This column is mandatory and cannot be removed when you edit the report.

Backup Time

Date and time when the primary backup is completed. This column is mandatory and cannot be removed when you edit the report.

SLP Completion Time

Date and time when the image is SLP-complete. This column is mandatory and cannot be removed when you edit the report. The Lag Time gives you an idea of how much time was required to complete the SLP and judge how fast or slow duplications occur. The Lag time is displayed in seconds. The Lag time for a specific image copy is computed by using data from the following columns and by using the following formula: Lag Time = SLP Completion Time Backup Time This column is mandatory and cannot be removed when you edit the report.

Lag Time (SLP Completion Time Backup Time)

Total Copies

Total number of copies in the OpsCenter database for the specific SLP and image on the selected master server (includes both complete copies and incomplete copies). Click the number (link) to view the SLP Status by Image Copy report. This column is mandatory and cannot be removed when you edit the report.

678

Reporting in OpsCenter About Report Templates descriptions

Copies Completed

The number of completed copies that are present in the OpsCenter database for the specific SLP and image on the selected master server. Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are complete for the selected master server. You can remove this column when you edit the report.

Copies Not Complete

Shows the number of incomplete copies in the OpsCenter database for the specific SLP and image on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by the following formula: Copies not Complete = Total Copies Copies Completed Click the number (link) to view the SLP Status by Image Copy report. A filtered view of the report appears that displays details for copies in the OpsCenter database that are incomplete for the selected SLP.

% Copy Complete

Percentage of completed copies in the OpsCenter database for the specific SLP and image on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated from the following columns of the SLP Status by Image report:

Copies Completed Total Copies

The contents of this column is calculated by using the following formula: Copies Completed / Total Copies * 100

Reporting in OpsCenter About Report Templates descriptions

679

Total Expected Size - all copies (MB)

Expected aggregate size of all copies for the selected SLP and image that are present in the OpsCenter database. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated by the following formula: Total Expected Size for all copies = (Number of copies) * (backup copy size)

Note: The total expected size for all copies is a front-end

size and is derived from the number of copies multiplied by the size of backup copy. The effects of deduplication, compression, or optimized deduplication on the Total Expected Size all copies are not considered in the SLP reports. Completed Copy Size (MB) Aggregate size of all the completed copies in the OpsCenter database for the specific SLP and image on the selected master server. You can remove this column when you edit the report.

Note: The Completed Copy Size is a front-end size. The

effects of deduplication, compression, or optimized deduplication on completed copy size are not considered in the SLP reports. Completed Copy Size (%) Percentage of completed copy size for the specific SLP and image on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated from the following columns of the SLP Status By Image report:

Completed Copy Size Total Expected Size all copies

The contents of Completed Copy Size (%) column is calculated by using the following formula: Completed Copy Size / Total Expected Size all copies * 100

680

Reporting in OpsCenter About Report Templates descriptions

Remaining Copy Size (MB)

Aggregate size of all remaining copies that are to be created for the specific SLP and image on the selected master server. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated in the following manner: (Remaining Copy Count) x (Size of Backup Copy1)

Note: The remaining copy size is a front-end size and is

derived from the number of remaining copies multiplied by the size of backup copy 1. The effects of deduplication, compression, or optimized deduplication on remaining copy size are not considered in the SLP reports.

You can use filters to view specific data in the SLP Status by Image report. The following filters are available when you edit the SLP Status by Image report:
Views Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers. You can select the following columns: SLP Name: Select one or more SLPs to view data for the selected SLPs. SLP status: Select SLP status for which you want to view data.

Master Server

Storage Lifecycle Policy

Policy

Select one or more policies to see data for the selected policies. Select one or more schedules to see data for the selected schedules. Select one or more clients to see data for the selected clients.

Schedule

Client

The default timeframe for this report is based on what timeframe is selected for the top-level report.

About the SLP Status by Image Copy report

The SLP status by Image Copy report is available as a drill-down report from the SLP Status, SLP Status by SLP, and SLP Status by Image report. You can view the SLP Status by Image Copy report when you click the links in the following columns:

Reporting in OpsCenter About Report Templates descriptions

681

Total Expected Copies Copies Completed (filtered view of the SLP Status by Image Copy report is shown) Copies Not Complete (filtered view of the SLP Status by Image Copy report is shown)

The SLP Status by Image Copy report shows how the image copies are created for different SLP destinations across different master servers. This report provides detailed information about the image copies that the SLP creates. This report provides details such as which copy is complete, which SLP is not complete and the specific copy operations that are pending. The SLP Status by Image Copy report comprises of the following columns:
Master Server (where the SLP lives) Name of the master server where the SLP runs. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The NetBackup master server must be of version 7.1 and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. SLP Name Name of the SLP that is associated with the selected master server. This column is mandatory and cannot be removed when you edit the report. SLP Version Version (link) that is associated with the specific SLP. This column is mandatory and cannot be removed when you edit the report. Click the version (link) to view the SLP Duplication Progress report. Data Classification Data classification that is associated with the SLP. This column is mandatory and cannot be removed when you edit the report. Policy Name Policy that is associated with the SLP. This column is mandatory and cannot be removed when you edit the report. Schedule that is associated with the NetBackup policy. You can remove this column when you edit the report.

Schedule Name

682

Reporting in OpsCenter About Report Templates descriptions

Client Name

Client name that is backed up by the SLP for the selected master server. This column is mandatory and cannot be removed when you edit the report. Image ID associated with the image. The image ID is unique for each image. This column is mandatory and cannot be removed when you edit the report. Click the image ID (link) to view the SLP Status by Image Copy report.

Image ID

Job ID

Job ID associated with the specific operation. This column is mandatory and cannot be removed when you edit the report. Origin Master Server is where the primary backup copy resides. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The origin master server and master server where the SLP lives (or is running currently) may be different if you duplicate to a remote master server. The Origin Master Server must be a NetBackup 7.1 master server and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report.

Origin Master Server (created the image)

Operation

The operation that is performed on an image copy like Duplication, Backup, Import etc. This column is mandatory and cannot be removed when you edit the report.

State

Current status of the copy like Complete, Not Started, In Process, Deleted, Paused. You can remove this column when you edit the report. Destination where a copy should reside as per the SLP definition. This column is mandatory and cannot be removed when you edit the report. Time when the copy expires. You can remove this column when you edit the report. Time when the copy is completed. This column is mandatory and cannot be removed when you edit the report.

Destination

Expiration Time

Copy/Import Completion Time

Reporting in OpsCenter About Report Templates descriptions

683

Lag Time (Copy Time Backup Time)

The Lag Time gives you an idea of how fast or slow duplications occur. The Lag time is displayed in seconds. This column is mandatory and cannot be removed when you edit the report.

Completed Copy Size (MB)

Aggregate size of all the completed copies in the OpsCenter database for the specific SLP and image on the selected master server. This column is mandatory and cannot be removed when you edit the report.

Note: The Completed Copy Size is a front-end size. The

effects of deduplication, compression, or optimized deduplication on completed copy size are not considered in the SLP reports.

You can use filters to view specific data in the SLP Status by Image Copy report. The following filters are available when you edit the SLP Status by Image Copy report:
Views Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers.

Master Server

684

Reporting in OpsCenter About Report Templates descriptions

Storage Lifecycle Policy

You can select the following parameters:

Duplication to Remote Master: If the value is Yes, then copy details for replication jobs are displayed.

Operation: Select one or more operations that you want to view. SLP name: Select one or more SLPs that you want to view. State: Select one or more states that you want to view.

Example: If you want to view all pending import operations, select the following parameters:

Operation = Import State = Not Started

Example: If you want to view the replication status for jobs, select the following parameters:

Duplication to Remote Master = Yes Operation = Duplication

Policy

Select one or more policies to see data for the selected policies. Select one or more schedules to see data for the selected schedules. Select one or more clients to see data for the selected clients. Enter the image ID for which you want to view data.

Schedule

Client

Images

The default timeframe for this report is based on what timeframe is selected for the top-level report.

About the SLP Status by Destinations report

The SLP Status by Destinations report is available as a drill-down report from the SLP Status by SLP report. You can view the SLP Status by Destinations report when you click the SLP name (link) in the SLP Status by SLP report. The SLP Status by Destinations report provides a summary of all the destinations for a specific SLP. You can view the SLP status by Destinations report to monitor

Reporting in OpsCenter About Report Templates descriptions

685

the SLP progress for each SLP destination. For example, you may want to know the image copies that are not complete for a specific SLP destination. The SLP Status by Destinations report comprises of the following columns:
Master Server (where the SLP lives) Name of the master server where the SLP runs. The SLP may run on the source master server or any of the destination master servers (in case of duplication to remote master). The NetBackup master server must be of version 7.1 and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. SLP Name Name of the SLP that you selected. This column is mandatory and cannot be removed when you edit the report. Version that is associated with the SLP. This column is mandatory and cannot be removed when you edit the report. Data classification that is associated with the SLP destination. This column is mandatory and cannot be removed when you edit the report. Origin Master Server (created the image) Origin Master Server is where the primary backup copy resides. The SLP may run on the origin master server or any of the destination master servers (in case of duplication to remote master). The origin master server and master server where the SLP lives (or is running currently) may be different if you duplicate to a remote master server. The Origin Master Server must be a NetBackup 7.1 master server and also added to the OpsCenter console. This column is mandatory and cannot be removed when you edit the report. Operation The operation that is performed on an image copy like Duplication, Backup, Import etc. for the specific SLP destination. This column is mandatory and cannot be removed when you edit the report. Retention Retention period that is associated with the specific SLP destination. This column is mandatory and cannot be removed when you edit the report.

SLP Version

Data Classification

686

Reporting in OpsCenter About Report Templates descriptions

Destination

Destination where an image should reside as per the SLP definition. This column is mandatory and cannot be removed when you edit the report.

Average Lag Time (Copy Time Backup Time)

The Average Lag Time gives you an idea of how much time is required to duplicate the primary copy to a particular destination for a specific SLP and judge how fast or slow duplications occur. The Average Lag Time is displayed in seconds. This column is mandatory and cannot be removed when you edit the report. Total number of copies in the OpsCenter database for the SLP and the specific SLP destination (includes both complete copies and incomplete copies). This column is mandatory and cannot be removed when you edit the report.

Total Expected Copies

Copies Completed

The number of completed copies that are present in the OpsCenter database for the SLP and the specific SLP destination. You can remove this column when you edit the report. Percentage of completed copies in the OpsCenter database for the SLP and the specific SLP destination. The column contents are calculated using data from the following columns of the SLP Status by Destinations report:

% Copy Complete

Copies Completed Total Copies

The contents of % Copies Complete column is calculated by using the following formula: Copies Completed / Total Copies * 100 This column is mandatory and cannot be removed when you edit the report.

Reporting in OpsCenter About Report Templates descriptions

687

Total Expected Size - all copies (MB)

Expected aggregate size of all copies for SLP and the specific SLP destination that are present in the OpsCenter database. This column is mandatory and cannot be removed when you edit the report. The column contents are calculated by using the following formula: Total Expected Size for all copies = (Number of copies) * (backup copy size)

Note: The total expected size for all copies is a front-end

size and is derived from the number of copies multiplied by the size of backup copy. The effects of deduplication, compression, or optimized deduplication on the Total Expected Size all copies are not considered in the SLP reports. Completed Copy Size (MB) Aggregate size of all the completed copies in the OpsCenter database for the SLP and the specific SLP destination. You can remove this column when you edit the report.

Note: The Completed Copy Size is a front-end size. The

effects of deduplication, compression, or optimized deduplication on completed copy size are not considered in the SLP reports. Completed Copy Size (%) Percentage of completed copy size for the SLP and the specific SLP destination. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated from the following columns of the SLP Status by Destinations report:

Completed Copy Size Total Expected Size all copies

The contents of Completed Copy Size (%) column is calculated by using the following formula: Completed Copy Size / Total Expected Size all copies * 100

688

Reporting in OpsCenter About Report Templates descriptions

Remaining Copy Size (MB)

Aggregate size of all remaining copies that are to be created for the SLP and the Size (MB) specific SLP destination. This column is mandatory and cannot be removed when you edit the report. The data for this column is calculated in the following manner: (Remaining Copy Count) x (Size of Backup Copy1)

Note: The remaining copy size is a front-end size and is

derived from the number of remaining copies multiplied by the size of backup copy 1. The effects of deduplication, compression, or optimized deduplication on remaining copy size are not considered in the SLP reports.

You can use filters to view specific data in the SLP Status by Image Copy report. The following filters are available when you edit the SLP Status by Image Copy report:
View Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers. You can select the following columns: Duplication to Remote Master: If the value is Yes, then SLPs that duplicate across master servers are displayed. Operation: Select one or more operations that you want to view SLP name: Select one or more SLPs that you want to view.

Master Server

Storage Lifecycle Policy

The default timeframe for this report is based on what timeframe is selected for the top-level report.

About the SLP Duplication Progress report

The SLP Duplication Progress report is available as a drill-down report from the SLP Status by SLP report. You can view the SLP Duplication Progress report when you click the SLP version (link) in the SLP Status by SLP report. The SLP Duplication Progress report is a graphical report that shows how the image copies are created for an SLP on a specific master server. This indicates how duplications are progressing for an SLP on a specific master server.

Reporting in OpsCenter About Report Templates descriptions

689

The SLP Duplication Progress report is in a bar chart format and shows the following data for each axis:

X axis shows all duplication destinations that are associated with the SLP Y1 axis bar charts show the percentage of images that are completed Y2 axis shows how many images are created.

Note: The SLP Duplication Progress report shows data for only one master server where that SLP version is running. You can also view the report data in a tabular format. To view the report details in a tabular format, click the link Show Chart as Table at the bottom of the report. You can edit the report to view specific data in the report. You can also save this report for reference. You can use filters to view specific data in the SLP Duplication Progress report. The following filters are available when you edit the SLP Duplication Progress report:
View Master Server Select a particular view to see data for the selected view. Select one or more master servers to see data for the selected master servers. Select an SLP to see data for the selected SLP. You can select only one SLP.

Storage Lifecycle Policy

The default timeframe for this report is based on what timeframe is selected for the top-level report.

Limitations of SLP reports

The data that is shown in the SLP reports is collected primarily from the EMM worklist and also from the NetBackup catalog. Hence it is important to understand how the EMM worklist functions. The functionality of the EMM worklist affects the data that is displayed in the SLP reports. The following sections provide an insight on SLP and EMM functionality and also list some limitations that are associated with the SLP reports.

About creating a storage lifecycle policy

While creating a storage lifecycle policy in NetBackup, you can specify the destinations where copies should be created. For an SLP, an image can be written to the initial destination as part of the following operations:

690

Reporting in OpsCenter About Report Templates descriptions

Backup

Import

You can define the Retention type for each SLP destination. You can select many retention types like Fixed (1, 2, 3 weeks), Expire after Duplication, Staged capacity managed etc. The following table explains the meaning of Fixed and Expire after Duplication retention types:
Fixed Fixed retention type means that the backup data is retained for a specific length of time before the backups are expired. When the retention period is reached, NetBackup deletes information about the expired backup. Expire after Duplication retention type means that the image expires after the dependent duplication is complete.

Expire after Duplication

When you are creating a NetBackup policy, the SLP that you created (like SLP1) can be selected as Policy Storage (storage unit). The SLP (SLP1) is executed when the policy runs.

About data collection from EMM

The data that is shown in the SLP reports is collected from the EMM worklist and the NetBackup catalog. The worklist is located in the EMM and contains metadata like how many copies need to be created, where they need to be created, when they are completed etc. In general, the copy data that is shown in the SLP reports (like Copies Completed, Completed Copy Size columns etc.) is based on the EMM worklist. EMM creates the worklist after a backup is complete based on lifecycle configuration parameters. Consider a case when you configure an SLP named SLP1: SLP1 performs the following operations:

Backup (Stu1) Duplication (Stu2) Duplication (Stu3)

After the backup is complete, a worklist that contains an entry for each copy is created in the EMM database. In this example, the EMM worklist has three copy entries (corresponding to the number of copies that are defined in the SLP). The EMM worklist is updated as and when a duplication job is processed (for example, State for the copy changes from Not Started to In Process to Complete).

Reporting in OpsCenter About Report Templates descriptions

691

SLP reporting limitations

OpsCenter collects data for SLP reports in the following phases: Table 11-15 Serial No.
1.

Phase
Initial Data Collection

Description
When a NetBackup 7.1 master server is added to the OpsCenter console, OpsCenter Server initially collects all data from the EMM worklist. After the initial data load, OpsCenter collects only the changed data after every 10 minutes.

2.

Periodic Data Collection

OpsCenter depends on the EMM worklist for SLP reporting. The following EMM behavior affects the data that is shown in the SLP reports:

If the Retention type of the SLP destination is Expire after Duplication, then EMM deletes the copy entry from the EMM worklist after duplication is complete. This behavior affects the initial data collection and periodic data collection for SLP reports. See Issues associated with initial data collection on page 692. See Issues associated with periodic data collection on page 692. If the Retention type of the SLP destination is Fixed, then EMM deletes the copy entry based on the Retention period that is specified in the policy. This behavior affects the initial data collection and periodic data collection for SLP reports. See Issues associated with initial data collection on page 692. See Issues associated with periodic data collection on page 692. If the SLP images reside on a tape drive, then EMM deletes the copy entry when the particular SLP is complete. This behavior affects the initial data collection and periodic data collection for SLP reports. See Issues associated with initial data collection on page 692. See Issues associated with periodic data collection on page 692. If you cancel an SLP that is in progress, then all the copy entries that are associated with this SLP image are deleted from the EMM worklist. This behavior affects the periodic data collection for SLP reports. See Issues associated with periodic data collection on page 692.

692

Reporting in OpsCenter About Report Templates descriptions

Issues associated with initial data collection

For initial data collection, the following potential issues can be seen in SLP reports due to the EMM behavior. Since initial data collection loads all the data from the EMM, it may have an image entry with missing copy entries. It is possible that the copy entries in the EMM worklist are deleted due to the following factors:

If the Retention type of an SLP destination is Expire after Duplication or Fixed. If duplications happen on a tape drive

The deletion of copies has the following affect on the data that is shown in specific SLP reports:

The SLP Duplication Progress report is in a bar chart format. The X axis shows all duplication destinations associated with the SLP; Y1 axis bar charts shows the percentage of images completed (% Images Count) and Y2 axis shows how many images are actually created (Completed Images Count). If a backup copy is deleted from the EMM worklist, then this report may show that the backup copy count is less than the duplication count. This is misleading. It is expected that when an SLP is complete, same number of copies should be created on all the destinations. Similarly the % Size Completed computation is inaccurate for this report. If a backup copy entry is deleted from the EMM worklist, the SLP Duplication Progress report will not show the backup bar chart. Similarly, if a duplication copy entry is deleted, the Duplication Progress report will not show the duplication bar chart. The SLP Status by Destination report will show incorrect copy sizes across destinations. The following columns of the SLP Status by Destination report show incorrect data:

Total Expected Size all copies (MB) Completed Copy Size (MB)

Issues associated with periodic data collection

When OpsCenter collects data periodically after every 10 minutes, the following potential problems can be seen in SLP reports. Consider a scenario when OpsCenter has collected the data for all copies associated with SLP1 which is in progress. However, before the next data collection happens one of the copy entries is removed from the EMM worklist (due to the EMM behavior). In this scenario, OpsCenter marks such copy entries as Complete if the image is SLP-complete during the next data collection cycle.

Reporting in OpsCenter About Report Templates descriptions

693

In this example scenario, you may see the following issues:

For all such copies that OpsCenter marks complete, the SLP Status by Image Copy report does not show any value for the Lag Time and the Copy End Time. If the last copy entry for an SLP is removed from the EMM worklist (due to EMM behavior), then the SLP Completion Time that is shown in the SLP Status by Image report is inaccurate.

Note: The same issues are seen if you cancel an SLP that is in progress (like SLP1). These issues occur because all the copy entries associated with this SLP image are deleted from the EMM worklist.

Known Issues
The following known issues are associated with the SLP reports:

When there are multiple copies in an SLP and two or more copies share the same destination, then only one-bar chart is shown for such copies in the SLP Duplication Progress report. The size of image copies for which Import is in a Not Started state, is not considered. Because of this behavior, the SLP Status, SLP Status by SLP, SLP Status by Client reports may display Completed Copy Size % as 100% while in reality there may be image copies for which the Import operation is in a Not Started state. If the Import is in a Not Started state for some image copies, the SLP Status by Destination report may show two rows for the same storage destination. This data is shown because there is insufficient data for image copies for which Import is in a Not Started state. The additional row is not shown once the Import operation is complete for all image copies.

Workload Analyzer
This section provides descriptions onthe workload Report Templates available in OpsCenter.

About Workload Analyzer

The Workload Analyzer is a report that gives 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..

694

Reporting in OpsCenter About Report Templates descriptions

The report comprises of four reports that are based on time, data transfer, job queue, and job throughput. Time is the point from when the jobs start, the periods for which the jobs are active, and the point when the jobs end. Job queue is based on the length of time, a job is in queue before the job is initiated. Job size is the amount of data that is moved from the target to the destination depending on the job type. Job size is also based on how much data is broken down and moved in a given hour. Job throughput is based on the data transmission rate. The Workload Analyzer reports consider only the jobs done for calcualtiing and generating the report. The calculation can result in a difference in data for the current hour and date. For example, a job that started in the past, and is in the queued state for a long time is not considered in the job queue report. It is considered onlt when it is complete. See About Workload Analyzer reports on page 694. See Generating a Workload Analyzer report on page 700.

About Workload Analyzer reports

The Workload Analyzer reports are based on time, queue, size, and throughput. The following reports are a part of the Workload Analyzer report:

Job Count Workload Analyzer: This report is based on the number of jobs running at a given period of time. The purpose of this report is to display the data that is based on time and load. You can determine the time for the job count on the basis of the start and end time of the job. Data for load is determined based on how many jobs are active during a given period of time. Calculations are done to determine the number of jobs that are active during a given period of time. For example, the following figure displays the job counts for a given period of time. (A) shows the jobs that start before the time interval and end after the time interval. (B) shows the jobs that start before the time interval and end during the time interval. (C) shows the jobs that start and end during the time interval. (D) shows the jobs that start during the time interval and end after the time interval.

Reporting in OpsCenter About Report Templates descriptions

695

Job Size Workload Analyzer: This report is based on the amount of data that is transferred during a given period of time. The calculation is based on the total amount of data that is backed up by the jobs divided by the time period. For example, in the following figure there are four jobs that have different durations across a four hour time period. The left-hand side displays the amount of data that's transferred during the four hour time period. The right-hand side of the report displays the start time and end time for each job, amount of data transferred, and duration. Job A is active for a period of four hours, it starts at 1:20 P.M. and ends at 4:20 P.M. During that period the total data that is transferred is 80,000 MB. You can calculate data transfer rate, multiply data transfer rate by the number of minutes during each hour when there is job activity. Job activity in the first hour is 20 minutes, in the second and third hour it is 60 minutes, and fourth hour it is 20 minutes. Jobs B, C, and D follow a similar pattern. Load is the sum of loads of all jobs during that hour. The yellow slot shows maximum activity and the data that is transferred is 115960 KB.

696

Reporting in OpsCenter About Report Templates descriptions

Job Queue Workload Analyzer: This report is based on the period for which, jobs are in a queue state before data back up begins.Queue time is calculated through the use of timestamps such as time taken to initiate the job, time taken to start and end the job. Jobs that have a high queue time are identified to reduce scenarios where many jobs with high queue time are initiated at the same time. The queuing is calculated at individual job level and then aggregated to the level where the report is generated.

Reporting in OpsCenter About Report Templates descriptions

697

Job Throughput Workload Analyzer: This report is based on the rate in Mbytes\Sec at which the data is transferred This calculation provides an important indicator to understand the performance. The throughput report is based on cross-hour calculation. The report displays accurate analysis of the data. Compared to the other workload reports, the totals for the rows of this report are averaged. The Start Write time ensures that the speed is only measured against the time in which, the actual data transfer takes place. This calculation ensures that the queue time is not considered. The queue report calculates the queue time. In the following figure, the throughput is calculated across four jobs that span for a period of three hours. One job belongs to Policy B and three jobs belong to Policy A. The green boxes indicate the time in which the write job occurs.

See Understanding the Workload Analyzer report template on page 697. See Generating a Workload Analyzer report on page 700.

Understanding the Workload Analyzer report template

The Workload Analyzer report template is a pre-fixed 168 hour reporting template. The template makes extensive use of color to display the analyzed data through the heat map technology. You can configure the color range. Report categories that include attributes such as backup server, media server, client, policy, provide a good means to understand the basics of workload and performance. All the

698

Reporting in OpsCenter About Report Templates descriptions

reports that comprise the workload analyzer report template are based on time. The following figure is a sample report template.

The highlights of the workload analyzer report template are as follows:

You can hover the mouse on each cell in the report to get details such as date, time, hour, and actual value of the hour. You can configure the range for each color. The color depicts the density of the jobs running at that hour. It also displays the number of minutes of queue time, the amount of data transferred, and the throughput rate. The deeper the color of the cell, the higher is the value in the cell. You can use the Report on feature to select entities for which, you require the data. For example, if you select Report on for a master server, the second column in the report displays data for the master server only. The entities include Backup Server, Media Server, Backup Client, Policy, Policy Type, Schedule, Job Type, Job Level, Job Error Code, Exit Status, Job Exit Code, Job Transport Type, Schedule \ Level Type, and Storage Unit. You can drill down to the next level in the report. The second column is hyper linked and provides the drill-down option. For example, from the master server you can drill down to client. A drill-down report is launched. You can drill-down to clients from the media server, policy, policy schedule, schedule, job type, job error code, job status, job level, transport type. Other drill-down options are policy type to policy, job status to job error code, view to next level down the view hierarchy. The last row on the report shows the total values of all the rows for the entire time span. The first column shows data for the entire week, whereas the hour column shows data for that particular hour for all entities. You can use various filters in the report. The filters include: Filter type
Time Filter View Master Server, Media Server

Description
Filter on Absolute or Relative time filter Filter on any view. Filter on available master servers and media servers.

Reporting in OpsCenter About Report Templates descriptions

699

Filter type
Client Policy Schedule Job

Description
Filter on available client. Filter on name and type of policy. Filter on schedules Filter on status, status code, transport type, type, and schedule or level type. Filter on the name. Filter on duration threshold and time basis.

Storage Unit Workload

You can use the Report on feature for different variables. The variables include Backup Server, Media Server, Backup Client, Policy, Policy Type, Schedule, Job Type, Job Level, Job Error Code, and Storage Unit You can drill down on any cell to know the details about the data.

The following drill down options are available for all the Workload Analyzer reports.

Master Server to Client Media Server to Client Policy Type to Policy

700

Reporting in OpsCenter About Report Templates descriptions

Policy to Client Policy ScheduletoClient Schedule to Client Job Type to Client Job Error Code to Client Job Status to Client (when Job Status <> Failure) Job Status to Job Error Code (when Job Status = Failure) Job Level to Client Transport Type to Client View to Next level down the view hierarchy

The colors in the report represent different data values, the information is aailable in the following table. Table 11-16 Color range
Idle

Color range values Value

Displays cells that are grey, which means there are no no active jobs assigned. Displays the value for data that has the color range between 1 - 10, the light yellow cells represent these values. Displays the value for data that has the color range between 11 - 50, the dark yellow cells represent these values. Displays the value for data that has the color range between 51 - 100, the orange cells represent these values. Displays the value for data that has the color range that is greater than 100, the red cells represent these valuues.

1 - 10

11 - 50

51 - 100

More than 100

See About Workload Analyzer reports on page 694.

Generating a Workload Analyzer report

You can generate the Workload Analyzer report using the Workload Analyzer report template from the reports tree. The report comprises of four reports that are based on time, data transfer, queue time, and throughput speed.

Reporting in OpsCenter About Report Templates descriptions

701

To generate the workload analyzer report

1 2

In the OpsCenter console, click Reports. On the Reports Template tab, click Create New Report. The reports are also available under the reports tree as shown in the following figure

3 4

On the Report Wizard, retain the default selection Create a report using an existng report templateand click Next. From the Select Report Template list, select the Workload Analyzer report you want to create and click Next.

702

Reporting in OpsCenter About Report Templates descriptions

Select the time frame from the Relative TimeFrame (beginning at) or Absolute TimeFrame (beginning at) options. The TimeFrame option displays the output for seven days for the previous week or the next week. The Relative Timeframe option also displays data from the date you choose, it can also be from the middle of a week. Absolute TimeFrame displays data for a week for the date you select. For example, if you select today's date, the data that is displayed is for the next week including today's date. The selection is for a week and there is no end time provided for selection.

6 7 8

Select the required filters and click Next. View the report and click Next. Enter a name and description in the Report name and Description text boxes. Select the location and click Save to save the report. Note: Open the saved report. Use the options Previous Week and Next Week to view data for the previous seven days or next seven days.

Exporting and emailing the Workload Analyzer report

The Workload Analyzer report can be exported in the HTML format. You can set the export location through the Report Export Location tab. See Setting report export location in OpsCenter on page 318. The report can be emailed only in the HTML format. Note: When the Workload Analyzer report is emailed, for Outlook Express, it does not show the correct alignment of the cells of the report.

Appendix

Additional information on PureDisk data collection

This appendix includes the following topics:

About AT configuration scenarios specific to PureDisk backup product Setting up a trust between the OpsCenter AB host and PureDisk SPA host

About AT configuration scenarios specific to PureDisk backup product

This section describes various configuration scenarios for Symantec Product Authentication Service (AT) that you should take into account before configuring PureDisk data collector. On a broader level, there can be two types of OpsCenter - PureDisk setups with respect to their AT root broker configurations:

Common AT root broker for OpsCenter server and PureDisk SPA See About Scenario 1: Common Root Broker on page 704. Different AT root broker for OpsCenter server and PureDisk SPA Note: In this type of configuration, you need to set up a bi-directional trust between the OpsCenter AB host and PureDisk SPA host. You need to establish trust between the authentication brokers of OpsCenter and PureDisk SPA for secure communication. This set up is a pre-requisite for PureDisk data collection from OpsCenter. See About Scenario 2: Different Root Brokers on page 705.

704

Additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product

About Scenario 1: Common Root Broker

This section talks about all scenarios where the AT root broker is common for OpsCenter server as well as PureDisk SPA. Figure A-1 describes a scenario where the AT root broker is configured on the PureDisk SPA host and OpsCenter server points to the same root broker. Thus for both product hosts, the AT root broker is common. You do not need to carry out any additional steps for PureDisk data collection. Figure A-1 Common root broker - root broker on PureDisk SPA
AT hierarchy Host B: PureDisk SPA AT Root Broker + Authentication Broker

Host A: OpsCenter Server AT Authentication Broker

Data collection

Figure A-2 describes a scenario where the AT root broker is configured on the OpsCenter server host and PureDisk SPA points to the same root broker. Thus for both product hosts, the AT root broker is common. Figure A-2 Common root broker - root broker on OpsCenter Server
AT hierarchy Host B: PureDisk SPA AT Authentication Broker

Host A: OpsCenter Server AT Root Broker + Authentication Broker

Data collection

Figure A-3 describes a scenario where the AT root broker is configured on the Host C and OpsCenter server host and PureDisk SPA point to this remote root broker. Thus for both product hosts, the AT root broker is common. Figure A-3 Common root broker - root broker on a remote host

Host C: AT Root Broker AT hierarchy Host A: OpsCenter Server AT Authentication Broker AT hierarchy Host B: PureDisk SPA AT Authentication Broker

Data collection

Additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product

705

About Scenario 2: Different Root Brokers

This section talks about all scenarios where the OpsCenter server and PureDisk SPA use different AT root brokers. Note: If OpsCenter and PureDisk have different AT root broker configurations, you need to set up a bi-directional trust between the OpsCenter AB host and the PureDisk SPA host. This set up is a pre-requisite for collecting PureDisk data from OpsCenter.

Note: Setting up trust between the PureDisk SPA host and OpsCenter AB host is a manual process. Refer to the Setting up a trust between PureDisk SPA host and OpsCenter AB host section. Setting up trust between the OpsCenter Authentication Broker host and PureDisk SPA host is accomplished automatically after PureDisk data collector is configured. If it is not successful, you need to do it manually. See Setting up a trust between the OpsCenter AB host and PureDisk SPA host on page 707. Figure A-4 describes a scenario where the OpsCenter server and PureDisk SPA use the AT root brokers that are configured on their respective hosts. Figure A-4 Different root brokers - root brokers on local hosts
Host B: PureDisk SPA AT Root Broker + Authentication Broker

Host A: OpsCenter Server AT Root Broker + Authentication Broker

Data collection

Note: If you have this kind of configuration, you need to set up a trust between the two root broker hosts, that is between Host A and Host B. Figure A-5 describes a scenario where the OpsCenter server and PureDisk SPA use the AT root brokers that are configured on two remote hosts.

706

Additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product

Figure A-5

Root brokers on remote hosts

Host C: AT Root Broker

Host D: AT Root Broker

AT hierarchy

Host A: OpsCenter Server AT Authentication Broker

Data collection

Host B: PureDisk SPA AT Authentication Broker

Figure A-6 describes a scenario where the OpsCenter server uses remote root broker and PureDisk SPA uses local root broker. Figure A-6 Remote root for OpsCenter server and local root for PureDisk

Host C: AT Root Broker

AT hierarchy Host A: OpsCenter Server AT Authentication Broker Host B: PureDisk SPA AT Authentication Broker

Data collection

Figure A-7 describes a scenario where PureDisk SPA uses remote root broker and OpsCenter server uses local root broker.

Additional information on PureDisk data collection Setting up a trust between the OpsCenter AB host and PureDisk SPA host

707

Figure A-7

Local root broker for OpsCenter server and remote for PureDisk

Host C: AT Root Broker

AT hierarchy Host A: OpsCenter Server AT Authentication Broker Host B: PureDisk SPA AT Authentication Broker

Data collection

Setting up a trust between the OpsCenter AB host and PureDisk SPA host
This section provides the steps that are required to set up trust between the OpsCenter AB (authentication broker ) host and PureDisk SPA host. Note: OpsCenter AB host is the host where the OpsCenter server is installed. If OpsCenter is installed in a clustered mode, the OpsCenter AB host is the host name that was provided as the remote AB host during the OpsCenter installation.

Note: Trust setup between the OpsCenter AB host and PureDisk SPA host is automatically carried out when you create a PureDisk data collector in OpsCenter. If the trust is not successfully established at this stage, carry out the manual steps as follows.

708

Additional information on PureDisk data collection Setting up a trust between the OpsCenter AB host and PureDisk SPA host

To set up a trust between the OpsCenter AB host and PureDisk SPA host

On the OpsCenter AB host, run the following command depending on the OpsCenter server operating system : These are the default directory paths.
Windows 32-bit C:\Program Files\VERITAS\Security\Authentication\bin\vssat setuptrust --broker <PureDiskSPAhost:port> --securitylevel high C:\Program Files (x86)\VERITAS\Security\Authentication\bin\vssat setuptrust --broker <PureDiskSPAhost:port> --securitylevel high /opt/VRTSat/bin/vssat setuptrust --broker <PureDiskSPAhost:port> --securitylevel high

Windows 64-bit

UNIX

The registered port for authentication is 2821. If the AT root broker is configured with another port number, contact your security administrator for more information. After successfully setting up a trust between the OpsCenter AB host and PureDisk SPA host, the following message is displayed:
setuptrust ------------------------------------------Setup Trust With Broker: PureDiskSPAhost

Appendix

Attributes of NetBackup data

This appendix includes the following topics:

Backup data attributes

Backup data attributes

This section lists all attributes pertaining to data that OpsCenter collects from NetBackup. You can select these attributes while generating custom reports. The following tables list all NetBackup attributes that OpsCenter collects.

Table B-1 Table B-2 Table B-3 Table B-4 Table B-5 Table B-6 Table B-7 Table B-8 Table B-9 Table B-10 Table B-11 Table B-12

710

Attributes of NetBackup data Backup data attributes

Table B-1 Data Attributes

Agent Server

Backup Job Attributes Sample Data

host.symantec.com

Explanation
The name of the server where a Backup Reporter data collection agent is installed Filled in by the user in the Job Reconciliation page to indicate why a job failed so others can see. The deduplication file factor for each PureDisk backup job. Meaning that for every 321 files that were backed up only one file was actually stored. (321 to 1 file deduplication rate) The number of files not needing to be backed up for every backup job in PureDisk because they were already stored with deduplication. Meaning that if 500 files were targeted for backup, only 44 were stored since the saving was 456. Within Backup Reporter there is the ability to mark a job as ignored (yes/no). If it is ignored it does not count towards things like success rate or time since last successful backup. This marking of a job as ignored is done in the "Reports > Explorers" section.

Backup job Comment

Host cannot be reached

Backup job File Count Deduplication Factor

321

Backup job File Count 456 Deduplication Savings

Backup job Is Ignored

Yes/No

Attributes of NetBackup data Backup data attributes

711

Table B-1 Data Attributes

Backup Job Attributes (continued) Sample Data

400 files

Explanation
The number of files that are processed in a PureDisk backup. Note that this number is not actually stored since it is before deduplication. The size in byes of a PureDisk backup job before deduplication. The deduplication size factor for each PureDisk backup job. Meaning that for every 567KB that were backed up only 1KB was stored. The number of KB's not needing to be backed up for every backup job in PureDisk because they were already stored with deduplication. Meaning that if 346KB were backed up, the savings of 345KB means only 1 KB was needed to be stored. Each directory under a job and it's type of backup. The transport that was used to move the backup from backup client to media server The number of times a backup job had to be attempted before being successful or reaching the maximum allowable number of retries

Backup job Protected File Count

Backup job Protected Size

200GB

Backup job Size Deduplication Factor

567

Backup job Size 345 Deduplication Savings

Backup job Sub Type

Catalog, File System, MS Exchange, NDMP, Sybase

Backup job Transport Type

LAN, SAN

Job Attempt Count

712

Attributes of NetBackup data Backup data attributes

Table B-1 Data Attributes

Job Client

Backup Job Attributes (continued) Sample Data

backup-client.symantec.com

Explanation
The name of a host being backed up as seen by a backup job The file system directory being backed up as seen by a backup job The amount of time in seconds for a backup to start and finish as seen by a backup job The date and time that a backup ended The exit code, status code, or error code for a particular job The time at which this job (the image that the job generates) will expire. The number of files a backed up during a backup job The group ID that the product group specifies. Note:The secondary ID and the Group ID are intended for the same purpose. These IDs group the jobs in some way that is useful in reporting.

Job Directory

C:\, /var, ALL_LOCAL_DRIVES

Job Duration

300 seconds

Job End Time

Tues 3/23/2008 03:34:43

Job Error Code

0,1,2,3

Job Expiration Time

Aug 01, 2008 22:03:48

Job File Count

300

Job Group ID

6114

Job Level

Full, Differential Incremental, User Backup

The Schedule Type for the backup job, Full, Incremental, Cumulative, User etc.

Attributes of NetBackup data Backup data attributes

713

Table B-1 Data Attributes

Job Primary ID

Backup Job Attributes (continued) Sample Data

5,234,234

Explanation
A unique number for each backup job in a backup domain that identifies a backup job When a unique job number is not enough to distinguish a job, a secondary ID may be used. For NBU, this field is the job Process ID The amount in KB that a backup job transferred from client to media server for backing up The date and time that a backup started A percent number that is calculated based on the number of jobs that were successful (NetBackup status 0) and partially successful (NetBackup status 1) divided by the total number of jobs ran in that period of time. Example: 98 successful jobs / 100 total jobs (2 failures) = 98% A percent number that is calculated based on the number of jobs that were successful (NetBackup status 0) divided by the total number of jobs ran in that period of time. Example: 98 successful jobs / 100 total

Job Secondary ID

5,234,235

Job Size

2048

Job Start Time

Tues 3/23/2008 02:34:43

Job Success Rate 98 (Complete and partial)

Job Success Rate (Complete only)

99

714

Attributes of NetBackup data Backup data attributes

Table B-1 Data Attributes

Job Throughput (Kbytes/sec)

Backup Job Attributes (continued) Sample Data

3,234

Explanation
The speed of a backup job in Kbytes/sec. This is the speed of the overall job which takes in to account transfer time from client to media server and media server to disk or tape storage. It is not just the speed of a tape drive. The type of operation done by the backup product The Schedule Type for the backup job grouped into just two options. Full vs. Other The name of the master server that executed the backup job The name of the media server that performed the backup job The name of the backup policy as seen by a backup job The name of the backup policy as seen by a backup job

Job Type

Backup, Restore, duplication, archive, label, erase

Level Type

Full, Differential Incremental, User Backup

Master Server

nbu-master.example.com

Media Server

nbu-media.example.com

Policy

Oracle Backup Policy, User Backup Policy, File System Backup Policy

Policy Description

Oracle Backup Policy, User Backup Policy, File System Backup Policy

Policy Description

This policy is for doing Oracle backups The user-defined description of a policy as seen by a backup job NetBackup Policy Domain, PureDisk Policy Domain The backup product that a backup policy executed a job from

Policy Domain Name

Attributes of NetBackup data Backup data attributes

715

Table B-1 Data Attributes

Policy Type

Backup Job Attributes (continued) Sample Data Explanation

Standard (UNIX), Windows-NT, Oracle, The type of policy as Exchange seen by a backup job NetBackup, PureDisk, TSM The backup product that performs backup, from which OpsCenter collects data The name of a schedule which resides within a policy as seen by a backup job A word description for each job that coorelates status codes to their english meaning. All failures are mapped to the word Failure The name of a storage unit which is choosen by a policy to receive and store backups. Storage Units are usually groupings of tape drives within a library or multiple disk locations that are grouped together in pools. This is the storage unit name that was used by a backup job and therefore may or may not exist in present time. The type of storage unit used and seen by a backup job

Product

Schedule

(user-defined), ex: Weekly-Fulls, Daily-Incrementals

Status

Success, Partial, Failure

Storage Unit Name

(user-defined), ex: tld0-hcart-0

Storage Unit Type

Disk, Media Manager (tape)

716

Attributes of NetBackup data Backup data attributes

Table B-2 Data Attributes

Backup Image Compression State

Backup Image Attributes Sample Data

Yes/No

Explanation
A yes/no property of if a backup image stored in the catalog was compressed or not. The date/time that a backup image copy is set to expire A yes/no property of if a backup image is expired or not. If it is expired it can no longer be restored and that space may be rewritten to by the backup application. If it is not expired it is available for restore. A yes/no property of if a backup image is the primary copy. If the image is a 2nd or greater copy this value would be no. The name of the backup server that performed the copy of a backup to a second location. A true/false property as to if the backup image copy was written using multiplexing or not (multiple clients/jobs streamed to one image) The type of storage unit that the backup image was copied to. This could be disk, tape etc.

Backup Image Copy Expiration Time

Mon 4/23/2008 4:32:34

Backup Image Copy Is Yes/No Currently Expired

Backup Image Copy Is Yes/No Primary

Backup Image Copy Media Server

backup-server.symantec.com

Backup Image Copy Multiplexed State

True/False

Backup Image Copy Storage Unit Type

Media Manager (tape), Disk

Attributes of NetBackup data Backup data attributes

717

Table B-2 Data Attributes

Backup Image Attributes (continued) Sample Data

30

Explanation
The number of fragments that make up a complete unexpired backup. A single backup can have 1 or a multiple of fragments which are blocks of data seperated by tape marks on tape or seperated in to separate files on the file system if written to disk. A unique ID or key for every backup stored in the catalog. This key or ID can be used to look up an image in the catalog for restore or other activity A yes/no property of if a backup image was encrypted between the backup client and backup media server. This value does NOT represent if tape drive or other encryption was used or not. The date and time that a backup image will expire. When a backup image expires it is no longer available for restore and the space that the backup occupied can be reused for additional backups (overwritten) The actual number of files that are stored within a backup image.

Backup Image Copy Unexpired Fragment Count

Backup Image Copy Unique ID

backupclient_23423

Backup Image Encryption State

Yes/No

Backup Image Expiration Time

Mon 4/23/2008 4:32:34

Backup Image File Count

432

718

Attributes of NetBackup data Backup data attributes

Table B-2 Data Attributes

Backup Image Attributes (continued) Sample Data

Mon 4/23/2008 4:32:34

Explanation
The date/time that the backup image fragment is set to expire A yes/no property of if the backup image fragment is expired or not. Even if a backup fragment is expired, that space can not be reused until the whole backup image is expired (disk) or the whole backup tape media is expired (tape) The true image restore status for a backup image fragment. True image restores allow a restore to take place at the directory level without overwriting files that weren't backed up but are still in the directory. For this to be possible a true image restore backup image must exist. The size of the backup image fragment. By default NetBackup uses 1TB fragments (ie no fragments) but this can be configured to different values A unique ID associated with every backup image fragment A yes/no property as to if the backup image is expired or not

Backup Image Fragment Expiration Time

Backup Image Yes/No Fragment Is Currently Expired

Backup Image Fragment Is TIR

TIR Info on Disk, TIR Rsv Synthetic Info on Disk

Backup Image Fragment Size

2048

Backup Image Fragment Unique ID

backupimagefragment_124

Backup Image Is Currently Expired

Yes/No

Attributes of NetBackup data Backup data attributes

719

Table B-2 Data Attributes

Backup Image TIR Status

Backup Image Attributes (continued) Sample Data

TIR Info on Disk, TIR Rsv Synthetic Info on Disk

Explanation
The true image restore status for a backup image. True image restores allow a restore to take place at the directory level without overwriting files that weren't backed up but are still in the directory. For this to be possible a "true image restore" backup image must exist. The type of backup image. Catalog being a NBU catalog image for disaster recovery The number of copies that exist for a primary backup image. These are copies that are unexpired and can be used for a restore. A unique ID or key for every backup stored in the catalog. This key or ID can be used to look up an image in the catalog for restore or other activity The date and time that the backup image was finished writing. The date and time that the backup image began to be written.

Backup Image Type

Regular, Catalog

Backup Image 1, 2, 3 etc. Unexpired Copy Count

Backup Image Unique backupclient_23423 ID

Backup Image Write End Time

Mon 4/23/2008 4:32:34

Backup Image Write Start Time

Mon 4/23/2008 4:32:34

720

Attributes of NetBackup data Backup data attributes

Table B-2 Data Attributes

Data Classification Master Server

Backup Image Attributes (continued) Sample Data

master-server.symantec.com

Explanation
The name of the server that classified the backup image in some sort of ranking (gold, silver, bronze etc) The name of the classification of data The number ranking that corresponds with the name of data classification. A 1 would mean the data is more important than a 2 for example.

Data Classification Name Data Classification Rank

Gold, Silver, Bronze, Non-DataClassification-Name 1,2,3,etc

Table B-3 Data Attributes

Attempt Duration

Backup Attempt Attributes Sample Data

3500

Explanation
The number in seconds that a backup was attempted The number in seconds that a backup was attempted The date and time that a backup attempt ended (each attempt is unique) The error code that the backup attempt finished with The number of files the backup attempted to process The number in KB for the amount an attempted backup tried to process

Attempt Duration

3500

Attempt End Time

Mon 4/23/2008 4:32:34

Attempt Error Code

0, 1, 2, 3 etc.

Attempt File Count

0, 1, 2, 3 etc.

Attempt Size

2048

Attributes of NetBackup data Backup data attributes

721

Table B-3 Data Attributes

Backup Attempt Attributes (continued) Sample Data

Mon 4/23/2008 4:32:34

Explanation
The start time that a backup attempt began A named status that maps to the error code numbers in the backup application (for example a status 0 in NetBackup is a success, a status 1 is partial and all other numbers are failures) The average success rate across all attempts in all backups. Example would be the average of 2 backups were each was attempted 3 times. The success rate would be the success rate average of the 3 attempts within each backup job. (Note that this is different than the success rate across all jobs which does not take in to account attempts) The speed of a backup attempt in Kbytes/sec. This is different than the overall KB/sec for a job which would take in to account all attempts.

Attempt Start Time

Attempt Status

Success, Partial, Failure

Attempt Success Rate 98%

Attempt Throughput

2048Kbytes/sec

722

Attributes of NetBackup data Backup data attributes

Table B-3 Data Attributes

Backup Attempt Attributes (continued) Sample Data

98%

Explanation
The average success rate across all attempts in all backups but also including partial successes (status 1 in NetBackup). Example would be the average of 2 backups were each was attempted 3 times. The success rate would be the success rate average of the 3 attempts within each backup job. (Note that this is different than the success rate across all jobs which does not take in to account attempts) The attempt number in a sequence. 1 would represent the first attempt, 2 would represent the second attempt etc. The date and time that a particular file was skipped over during a backup The status code for why that file was skipped (usually a status 1) The reason a file was skipped. (Usually because file was in use) The actual file name that was skipped over during a backup.

Backup Attempt Partial Success Rate

Backup Attempt Sequence

1, 2, 3

Backup Skipped File Time

Mon 4/23/2008 4:32:34

Skipped File Code

Skipped File Reason

File is open by another process

Skipped File Name

C:\Windows\an_open_file.dll

Attributes of NetBackup data Backup data attributes

723

Table B-4 Data Attributes

Backup Policy Attributes Sample Data Explanation

The host name of the backup application host that contains the backup policy. In the case of NetBackup this is the master server. The name of a backup policy that exists in the backup application. Note that this is similar and can be the same as the backup job Attribute: Policy which shows what policy the backup job was executed from. It is different though since this Policy Name simply means that this Policy exists not that anything was executed from it yet.

Backup Policy Domain nbu-master.example.com Master Server

Backup Policy Name

Oracle Backup Policy, User Backup Policy, File System Backup Policy

Backup Policy Type

Standard (UNIX), Windows-NT, Oracle, The type of backup Exchange policy that exists in the backup application. Note that this is different than the backup job Attribute: Policy Type

Table B-5 Data Attributes

File System Attributes Sample Data Explanation

User defined field. Can be one of Mission Critical, Business Critical or Business Support A user defined field for an object ID of the file system. Typically used as a pairing with an asset management database

Business Classification Business Critical

File System: OID

asset123 etc.

724

Attributes of NetBackup data Backup data attributes

Table B-5 Data Attributes

Filesystem Name

File System Attributes (continued) Sample Data Explanation

C:\Documents and Settings\All Users\ The file system directory being backed up. NTFS, UFS, ZFS, EXT3 A user-defined field (this is not collected automatically) of what type of file system was backed up.

Filesystem Type

Table B-6 Data Attributes

Host Architecture

Host Attributes Sample Data

SPARC, x86

Explanation
User defined field (this is not automatically collected) for filling in architecture type such as x86, x86-64, SPARC, POWER, PA-RISC, IA64 etc A user defined field for inserting any extra information regarding a host A user defined field for inserting an object ID from an asset management database The name of the host object that contains file systems. The version of the operating system. Usually grouped with Operating System name since this will have values like 10 (i.e. Solaris 10), or 2003 (i.e. Windows 2003)

Host: Misc Info

Pete's server

Host: OID

asset123, etc.

Hostname

hostname.example.com

O.S. Version

2003, 10

Attributes of NetBackup data Backup data attributes

725

Table B-6 Data Attributes

Operating System

Host Attributes (continued) Sample Data

Windows, Solaris

Explanation
The operating system name of the host

Table B-7 Data Attributes

Agent Server

Backup Media Attributes Sample Data

ops-agent.example.com

Explanation
The name of the OpsCenter agent that collected the media information. The date/time that a piece of media was first allocated or had it's first backup written to it. Once the media expires it will have a new allocation date/time when it is reused How much is left on tape in KB. Value here per sample is either the free capacity if the media is active, or 0 otherwise. Total capacity of the tape in KB. Value here per sample is either the total capacity if the media is active, or 0 otherwise. The full barcode as ready by the physical robot. This can be longer than the 6 characters used by a NetBackup Media. The date/time that a backup media is set to expire

Backup Media Allocation Time

Mon 3/4/2008 3:34:34

Backup Media Available Free Capacity

500,000 KB

Backup Media Available Total Capacity

19,000,000KB

Backup Media Barcode JFP000L2

Backup Media Expiration Time

Mon 3/4/2008 3:34:34

726

Attributes of NetBackup data Backup data attributes

Table B-7 Data Attributes

Backup Media Free Capacity

Backup Media Attributes (continued) Sample Data

500,000 KB

Explanation
How much is left on tape in KB. This number may be estimated using an algorithm. A yes/no property of a particular tape indicating whether the tape has been sampled in the last two collections. A yes/no property of a particular tape indicating whether it can still be written to. A yes/no property of if the backup media exists in the current configuration (and not historical) A yes/no property of if the backup media has expired data on it or not A yes/no property of if the backup media is marked as full (no more backups can be written to it)

Backup Media Is Active Yes/No

Backup Media Is Available

Yes/No

Backup Media Is Current

Yes/No

Backup Media Is Data Expired

Yes/No

Backup Media Is Full

Yes/No

Attributes of NetBackup data Backup data attributes

727

Table B-7 Data Attributes

Backup Media Is Imported

Backup Media Attributes (continued) Sample Data

Yes/No

Explanation
A yes/no property of if the backup media was imported. Imported media simply means that this paticular backup domain did not originally write the data to the media. This could be due to disaster recovery where the catalog could not be moved from an existing domain so the tapes were read individually to determine what data was on them. It also is commonly used to import Backup Exec media to NetBackup. A yes/no property of if the physical media is expired or not. Once all the backup images (data) has been expired on a tape that entire cartridge is marked as Physically Expired=Yes and it can be overwritten or used by future backups. Since capacity of a tape is often estimated using an algorithm. This specifies whether it was actually calculated, or provided exactly by the DP product. A date/time that the backup media was last used to be read (restored)

Backup Media Is Physically Expired

Yes/No

Backup Media Is Total Yes/No Capacity Estimated

Backup Media Last Read Time

Mon 3/4/2008 3:34:34

728

Attributes of NetBackup data Backup data attributes

Table B-7 Data Attributes

Backup Media Last Write Time

Backup Media Attributes (continued) Sample Data

Mon 3/4/2008 3:34:34

Explanation
A date/time that the backup media was last used to be written to (duplicates, backups) The physical slot number that a given piece of media resides in A yes/no property of if a given piece of tape media will allow for multiple expiration dates. Multiple expiration dates means that the whole tape can not be reused until the last backup has expired on the media. A yes/no property of if multiplexing is allowed on a piece of tape media. Multiplexing means that multiple clients were multiple clients or jobs were backed up to one image so that particular image could have more than one client inside it. Calculated value representing (available free capacity /available total capacity ) in percentage Calculated value representing (free capacity total capacity ) in percentage

Backup Media Library 1, 2, 3 etc. Slot Number

Backup Media Multiple Yes/No Retention Levels Allowed

Backup Media Multiplexing Allowed

Yes/No

Backup Media Percent 0-100% Available Free Capacity

Backup Media Percent 0-100% Free Capacity

Attributes of NetBackup data Backup data attributes

729

Table B-7 Data Attributes

Backup Media Attributes (continued) Sample Data Explanation

Calculated value representing (used capacity / total capacity) in percentage The date/time that a piece of media will physically expire (all images on the media) and be able to be reused

Backup Media Percent 0-100% Used Capacity

Backup Media Physical Mon 3/4/2008 3:34:34 Expiration Time

Backup Media Retention Level

63072000.00, 31536000.00, 1209600.00 The retention level of the media in number of seconds. Divide by 86400 to get the retention level in days Mon 3/4/2008 3:34:34 The date/time that all the media information was collected from the backup application to OpsCenter. History is kept so a history of the state of all media can be determined. The type of storage for a given piece of media (disk or tape) Total capacity of the tape in KB. This number may be estimated using an algorithm. The density or type of media. This is used to match what drives the media can go in for a mixed media environment. The number of images that are unexpired on a given piece of media

Backup Media Snapshot Time

Backup Media Storage Disk, Tape Type

Backup Media Total Capacity

19,000,000 KB

Backup Media Type

HCART, DLT, 8MM etc.

Backup Media Unexpired Image Count

1, 2, 3 etc.

730

Attributes of NetBackup data Backup data attributes

Table B-7 Data Attributes

Backup Media Attributes (continued) Sample Data

500,000 KB

Explanation
Amount in KB used up in the tape. This value is provided by the DP product and is NOT estimated.

Backup Media Used Capacity

Backup Media Volume User defined but defaults to things like A user defined field for Group Name 000_00002_TLD grouping volumes. By default NetBackup assigns the robot number and type so that TLD(2) would read 000_00002_TLD Backup Media Volume /disk_staging_file_system/, Path C:\disk_staging\ The path on disk where backup images are stored. Specific to NetBackup 6.5 - this is the high water mark that is set for a Flexible Disk pool, OpenStorage disk pool or PureDisk backend storage pools. When this threshold is reached by the file system on the disk pools backups will not be attempted to that disk location since it will be considered full. Specific to NetBackup 6.5 - this is the low water mark that is set for a Flexible Disk pool, OpenStorage disk pool or PureDisk backend storage pools. When this threshold is reached by the file system on the disk pools backups will not be sent to the location as often

Disk Pool High Water Mark

95%

Disk Pool Low Water Mark

80%

Attributes of NetBackup data Backup data attributes

731

Table B-7 Data Attributes

Disk Pool Master Server

Backup Media Attributes (continued) Sample Data

nbu-master.example.com

Explanation
The name of the NetBackup master server that the disk pool belongs to The name of the disk pool which defaults to the disk array string or a user defined value The raw size is the size of the disk volume(s) in a disk pool. Raw size does not mean you can actually write to that amount (that's what usable size is) but just tells you there is more possible disk space that could be allocated from raw to usable. The type of flexible disk that the pool is The date/time that a snapshot was taken to produce the backup image that exists in the disk pool Similar to tape drive status, this tells if the disk pool is UP meaning it is usable and can be used or DOWN meaning it is not usable. When in the DOWN state jobs will not attempt to use the disk pool.

Disk Pool Name

netappfi::fas3050-1a, DDPool, etc.

Disk Pool Raw Size

69,990.40

Disk Pool Server Type AdvancedDisk, SharedDisk

Disk Pool Snapshot Time

Mon 3/4/2008 3:34:34

Disk Pool Status

UP, DOWN

732

Attributes of NetBackup data Backup data attributes

Table B-7 Data Attributes

Backup Media Attributes (continued) Sample Data

1,208,893.44

Explanation
The usable size is the size of the formatted file system and tells you how much data can be written to the disk pool The number of disk volumes that make up the disk pool The type of tape media as defined by the backup application. For NetBackup this is also called the density and specifies what types of drive the tape can go in. Optical media header size of a backup image The Media ID for a given piece of media, usually a subset of the barcode. For NetBackup this is a 6-digit ID. The number of backup images on a given piece of tape media or disk pool Logical block address of the beginning of the block that a backup image exists The number of times a given piece of backup media has been used for restores. Optical media sector size of a backup image.

Disk Pool Usable Size

Disk Pool Volume Count

Media Density

HCART, DLT, 8MM etc.

Media Hsize

1024

Media ID

JFP000

Media Image Count

54

Media L Offset

2048

Media Restore Count

0, 1, 2, 3, etc.

Media Ssize

1024

Attributes of NetBackup data Backup data attributes

733

Table B-7 Data Attributes

Partner

Backup Media Attributes (continued) Sample Data

A/B

Explanation
The ID of the opposite side of a optical platter. If on side A of a platter this would show Side B The backup product that this piece of media belongs to

Product

NetBackup, TSM

Status

Active, Non-active, Suspended, Frozen The status of a given piece of media. Active meaning it is being used at a given point in time, Frozen meaning errors have occurred on the tape media and it is no longer being used for backups, etc. 1, 2, 3, 4 etc. The volume pool ID which automatically starts at 1 for the default pool "NetBackup". Things like Scratch Pools or onsite/offsite pools are typically also used and these all have unique volume pool ID's. Many encryption solutions such as Decru and IBM use the volume pool ID to determine what backups to encrypt or not This user defined field is the name of the volume pool that media is placed in to. The default is NetBackup but many others are typically created to segment tapes in to groups

Volume Pool ID

Volume Pool Name

NetBackup, Scratch, CatalogBackup, MSEO, WORM, etc.

734

Attributes of NetBackup data Backup data attributes

Table B-7 Data Attributes

Volume/EMM Database Server

Backup Media Attributes (continued) Sample Data

nbu-master.example.com

Explanation
The name of the Volume Database (pre-NetBackup 6.) or EMM server (NetBackup 6.0+). This is typically the NBU Master but doesn't have to be in the case where multiple masters are sharing the same EMM server.

Table B-8 Data Attributes

Tape Library Attributes Sample Data

NetBackup, TSM

Explanation
The backup application that controls the tape drive The server host name that the OpsCenter agent is installed on that is used to collect tape drive information. The device database server that is controlling the particular library. This is the Enterprise Media Manager server (EMM) in NetBackup 6.0+ or the device control host in 5.1 and below. The manufacturer as determined by the SCSI inquiry string in the backup application. The serial number, unique, to each tape library

Tape Library Agent Product

Tape Library Agent Server

ops-agent.example.com

Tape Library Device Database Server

NBU-device-host.example.com

Tape Library Manufacturer

STK, Quantum, IBM etc.

Tape Library Serial Number

ADIC203100468_LL0

Attributes of NetBackup data Backup data attributes

735

Table B-8 Data Attributes

Tape Library Slot Count

Tape Library Attributes (continued) Sample Data

40, 120, 360

Explanation
The total number of slots that exist in a tape library

Tape Library Type

Tape Library DLT, Tape Library 8MM, The type of tape library Tape Library ACS (TLD, ACS, 8MM, 4MM, TLM, TLH etc) 0, 1, 2 etc. The unique number given to each tape library in the EMM database. This ID is put together with the library type in the NBU GUI to show TLD(0), TLD(1) etc.

Tape Library Unique ID

Table B-9 Data Attributes

Name

Tape Drive Attributes Sample Data

IBM.ULTRIUM-TD2.000

Explanation
The name of a tape drive as given by the backup application, usually default names are based on SCSI inquiry strings that contain the manufacturer name and model number The number of a tape drive as given by the backup application which is unique for each physical drive (a number could be shared between media servers though) A simple true/false on weather the tape drive is shared across backup servers or not

Number

0, 1, 2, 3 etc.

Shared

true/false

736

Attributes of NetBackup data Backup data attributes

Table B-9 Data Attributes

Tape Drive Device Host

Tape Drive Attributes (continued) Sample Data

NBU-device-host.example.com

Explanation
The device host (Media Server) that the tape drive is connected to. A simple true/false on weather the tape drive exists in the current configuration (true) or if it is historical and no longer exists (false) The unique serial number for a physical tape drive The storage unit that the tape drive is assigned to The type of tape drive as defined by the backup application. For NetBackup this is also called the density and specifies what types of tape can go in the drive. The tape drive number inside the library

Tape Drive Is Current

true/ false

Tape Drive Serial Number

768ZD03034

Tape Drive Storage Unit Name Tape Drive Type

dcdell214-dlt-robot-tld-0

hcart, hcart2, dlt, 8mm etc.

Tape Drive Unique ID for Library

1, 2, 3, 4, 5, 6 etc.

Table B-10 Data Attributes

Tape Usage Attributes Sample Data

Storage Unit Tape Group

Explanation
The storage unit group that the storage unit that the tape drive belongs to The host (Media Server) that the tape drive is assigned to for use at time of tape drive information collection

Storage Unit Group Name

Tape Drive Assigned

nbu-host.example.com

Attributes of NetBackup data Backup data attributes

737

Table B-10 Data Attributes

Tape Drive Control

Tape Usage Attributes (continued) Sample Data Explanation

TLD, ACS, DOWN-TLD, DOWN-ACS etc. The robot type that is controlling the tape drive and it's associated status of up or down at time of tape drive information collection true / false A true / false for if the tape drive was enabled at the time of tape drive information collection A true / false for if the tape drive was in use at the time of tape drive information collection The tape that was in the drive at the time of tape drive information collection The date and time that the tape drive information was collected

Tape Drive Enabled

Tape Drive In Use

true / false

Tape Drive Recorded Media ID

VT0036

Tape Drive Snapshot Time

Apr 05, 2008 22:57:17

Table B-11 Data Attributes

Backup Log Agent Server

Backup Log Attributes Sample Data

ops-server.example.com

Explanation
The host name of the OpsCenter server where the database and web interface resides

Backup Log Message

backup of client dcdell211 exited with The detailed status status 71 (none of the files in the file messages for each job list exist) nbu-host.example.com The host server with the backup application that logged the error message

Backup Log Source Host

738

Attributes of NetBackup data Backup data attributes

Table B-11 Data Attributes

Backup Log Client

Backup Log Attributes (continued) Sample Data

nbu-client.example.com

Explanation
The backup client that was associated with the logged error message The process or daemon name that wrote the error message The group ID that can be specified by the backup product to group them in a certain way. Note:The secondary ID and the Group ID are basically intended for the same purpose, that is to group the jobs in some way that is useful in reporting. A unique number for each backup job in a backup domain that identifies what backup job caused the error message to be logged The date/time that the error message or log was written to The backup application name that caused the error message to be created The severity code of the error message The code representing the type of the log and error message The version of the log/error message

Backup Log Daemon Name

bptm, ndmpagent, nbpem, bpbrm

Backup Log Job Group 5980 ID

Log Primary ID

6021

Log Time

Mon 3/4/2008 3:34:34

Product

NetBackup, TSM

Severity Code

1, 2, 3, 4 etc.

Type Code

1, 2, 3, 4 etc.

Version

1, 2, 3, 4 etc.

Attributes of NetBackup data Backup data attributes

739

Table B-12 Data Attributes

Agent Monitoring Attributes Sample Data

1, 2, 3, 4 etc.

Explanation
A unique number for each data collection agent under the OpsCenter server The host name of the OpsCenter data collection agent The date and time of the last heartbeat from the data collection agent to the OpsCenter server The host name of the OpsCenter server where the database and web interface resides The number of seconds since the last heartbeat from the data collection agent to the OpsCenter server

Agent Configuration ID

Agent Host

ops-agent.example.com

Last Heartbeat

May 04, 2008 10:52:28

Server

ops-server.example.com

Time Since Agent Last 44 Heartbeat

740

Attributes of NetBackup data Backup data attributes

Appendix

Man pages for CLIs

This appendix includes the following topics:

changeDbPassword changeVxATProperties configurePorts dbbackup dbdefrag opsadmin opsCenterAgentSupport opsCenterSupport runstoredquery startagent startdb startgui startserver stopagent stopdb stopgui stopserver

742

Man pages for CLIs changeDbPassword

changeDbPassword
changeDbPassword This script changes the OpsCenter database password. This

is supported only for DBA user and not for guest and server passwords.

SYNOPSIS
changeDbPassword [--restoreDefaultPassword] | [-h|-?|--help]

DESCRIPTION
Sybase SA (SQL Anywhere) database management system is used to store the OpsCenter data. You require a user name and a password to access the database. The following database user account is shipped with OpsCenter:
dba The database administrator account. The dba account is required by the database queries that are used to update the database schema or upgrade to a new product version.

When the tool changes the dba password, it updates a configuration file on the file system so that the server can still access the database. The password is encrypted before it is stored in the configuration file. However, since the server needs to retrieve the password it cannot be stored with a one-way hash. Thus, someone could obtain the password. When the tool is run, the system administrator is advised to check the permissions on the configuration file to ensure that only an administrator can read the file.

OPTIONS
--restoreDefaultPassword

Resets DBA password to the default password.

--h|-?|--help

Shows the CLI usage statement and exits.

NOTES
Enter the following command to change the database password on Windows:
INSTALL_PATH\OpsCenter\server\bin\changeDbPassword.bat

You are prompted to enter the current and the new password. Enter the current and the new password. Enter the following command to change the database password on UNIX:

Man pages for CLIs changeDbPassword

743

/opt/SYMCOpsCenterServer/bin/changeDbPassword.sh

You are prompted to enter the current and the new password. Enter the current and the new password.

744

Man pages for CLIs changeVxATProperties

changeVxATProperties
changeVxATProperties This script configures the Symantec Product

Authentication Service (AT) Server parameters.

SYNOPSIS
changeVxATProperties

DESCRIPTION
The changeVxATProperties script prompts you to enter the following details:

Authentication Service Host Name Authentication Service Port Number Authentication Service Domain Name Authentication Service User Name Authentication Service Password

OPTIONS
Not applicable

NOTES
Enter the following command to configure AT parameters on Windows:
INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat

Enter the following command to configure AT parameters on UNIX:

/opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

Man pages for CLIs configurePorts

745

configurePorts
configurePorts This script is used to configure Web server ports on UNIX or

Linux systems.

SYNOPSIS
configurePorts.sh [-status]|[-httpPort <httpPort>][-httpsPort <httpsPort>][-shutdownPort <shutdownPort>]

DESCRIPTION
The configurePorts script is used for the following purposes:

For configuring http, https and Tomcat shutdown ports For querying the current values for the above ports

OPTIONS
-status

Queries the current values for http, https, and Tomcat shutdown ports This option is to be used exclusive of other attributes.
-httpPort <httpPort>

Modifies the httpPort to the new value in web.xml of Tomcat

-httpsPort <httpsPort>

Modifies the httpsPort to the new value in web.xml of Tomcat

- shutdownPort <shutdownPort>

Modifies the shutdownPort to the new value in web.xml of Tomcat

NOTES
To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run the following command on Windows:
INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.cmd -status

Run the following command on UNIX:

/opt/SYMCOpsCenterGUI/bin/goodies/configurePorts.sh -status

746

Man pages for CLIs dbbackup

dbbackup
dbbackup This script backs up the OpsCenter database.

SYNOPSIS
dbbackup <DB_BACKUP_DIR> [-v | -restore]

DESCRIPTION
dbbackup is a script used for backing up the OpsCenter database.

OPTIONS
DB_BACKUP_DIR

(Required) DB_BACKUP_DIR is the directory where the OpsCenter database is backed up to, or restored from. DB_BACKUP_DIR should be an absolute path.
-v

Option to validate the database after backup

- restore

Option to restore database from backupDir to the current database directory.

NOTES
On Windows, you perform backups with the dbbackup.bat batch file. The backup script creates the following files in the backup directory: vxpmdb.db and vxpmdb.log Data spaces are started when the main database is started; therefore, starting and stopping the data space file is not required.

EXAMPLES
The following command backs up the OpsCenter database to the my_db_backups directory on Windows:
INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat C:\my_db_backups

The following command backs up the OpsCenter database to the my_db_backups directory on UNIX:
/opt/SYMCOpsCenterServer/bin/dbbackup.sh /my_db_backups

Man pages for CLIs dbdefrag

747

dbdefrag
dbdefrag This script defragments the OpsCenter database.

SYNOPSIS
dbdefrag

DESCRIPTION
The dbdefrag script is used to defragment the OpsCenter database.

OPTIONS
Not applicable

NOTES
To defragment the OpsCenter database run the following commands. Run the following command on Windows:
INSTALL_PATH\OpsCenter\server\bin\dbdefrag.bat

Run the following command on UNIX:

/opt/SYMCOpsCenterServer/bin/dbdefrag.sh

748

Man pages for CLIs opsadmin

opsadmin
opsadmin This script is used to monitor/start/stop the OpsCenter services on

UNIX or Linux systems

SYNOPSIS
opsadmin.sh {start|stop|monitor}

DESCRIPTION
The opsadmin script is used for monitoring/starting/stopping the OpsCenter services.

OPTIONS
start

Starts all OpsCenter services. These services include OpsCenter database, OpsCenter server, and Web server services.
stop

Stops all OpsCenter services. These services include OpsCenter database, OpsCenter server, and Web server services.
monitor

Monitors all OpsCenter services and also AT (Symantec Product Authentication Service) and PBX (Symantec Private Branch Exchange)services

NOTES
opsadmin opsadmin.sh resides by default in the /opt/SYMCOpsCenterServer/bin directory.

EXAMPLES
EXAMPLE 1 The following command starts all OpsCenter services:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

EXAMPLE 2 The following command monitors OpsCenter services:

Man pages for CLIs opsadmin

749

/opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor

750

Man pages for CLIs opsCenterAgentSupport

opsCenterAgentSupport
opsCenterAgentSupport This script collects OpsCenter Agent configuration

files and logs.

SYNOPSIS
opsCenterAgentSupport

DESCRIPTION
The opsCenterAgentSupport script collects OpsCenter Agent configuration files and logs for troubleshooting.

OPTIONS
Not applicable

NOTES
Run the following commands to execute the support scripts for OpsCenter Agent. Run the following command on Windows:
INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport.bat

Run the following command on UNIX:

/opt/SYMCOpsCenterAgent/bin/opsCenterAgentSupport.sh

You can view the following status messages on the command prompt:
Stopping the OpsCenter Agent Service... Support Directory Exists. This will be deleted... Support Directory Deleted... Created Support Directory... Zipping Support Folder... Please collect Support.zip file from C:\PROGRA~1\Symantec\OPSCEN~1\Agent\temp\support.zip Starting the OpsCenter Agent... C:\Program Files\Symantec\OpsCenter\Agent\bin>

Man pages for CLIs opsCenterSupport

751

opsCenterSupport
opsCenterSupport This script collects OpsCenter server configuration files and

logs for troubleshooting.

SYNOPSIS
opsCenterSupport

DESCRIPTION
opsCenterSupport is a script used for collecting OpsCenter server configuration

files and logs for troubleshooting.

OPTIONS
Not applicable

NOTES
Run the following command to collect OpsCenter server configuration information: Run the following command on UNIX:
/opt/SYMCOpsCenterServer/bin/opsCenterSupport.sh

Run the following command on Windows:

INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport.bat

You can view the following statuses on the command prompt:

Support Directory Exists. This will be deleted... Support Directory Deleted... Created Support Directory... SupportDir=E:\OPSCEN~1\OPSCEN~1\server\temp\support Collecting Installed Paths Collecting System Properties Collecting Memory & Processor Properties Collecting Disk Allocation for OpsCenter Installed Drive Collecting Directory Structure for OpsCenter Collecting version file Collecting Version File... Getting Customized Collections...

752

Man pages for CLIs opsCenterSupport

Do you want to Collect Configuration files [y/n]: (y)y Do you want to Collect Application Log files [y/n]: (y)y Do you want to Collect OpsCenter GUI(147) Log files [y/n]: (y)y Collecting 147 files... Do you want to Collect OpsCenter Server(148) Log files [y/n]: (y)y Collecting 148 files... Do you want to Collect db Log files [y/n]: (y)y Collecting db logs... Do you want to Collect WebServer Log files [y/n]: (y)y Collecting WebServer logs... Do you want to Collect setEnv file [y/n]: (y)y Collecting setenv file... Do you want to Collect Database files [y/n]: (y)y Collecting vxpmdb file... Collecting vxpmdb.log file... If this is an Upgrade scenario Do you want to Collect Old Database files and logs [y/n]: (y)y Old dbfiles are not present in the path, hence not collected... Collecting upgrade logs... If this is an install scenario Do you want to Collect Installation Logs [y/n]: (y)y Zipping Support Folder... Please collect Support.zip file from E:\OPSCEN~1\OPSCEN~1\server\temp\support.zip

Man pages for CLIs runstoredquery

753

runstoredquery
runstoredquery

SYNOPSIS
runStoredQuery <Report Name> <User Name> <Domain Name> <Domain Type> [<Output Type> pdf | csv]

DESCRIPTION
The runstoredquery script runs saved customSQL and the OpsCenter Administrator generates output in the desired format.

OPTIONS
Report Name

Name of the report (surrounded with double-quotes) Example: runStoredQuery "My Report" admin OpsCenterUsers vx pdf
User Name

Name of the user who has saved the report

Domain Name

Domain name for the user

Domain Type

Domain type for the user

Output Type

Report output type (pdf/csv). The default is csv.

EXAMPLE
runStoredQuery "My Report" admin OpsCenterUsers vx pdf

754

Man pages for CLIs startagent

startagent
startagent This script starts the OpsCenter Agent service.

SYNOPSIS
startagent

DESCRIPTION
The startagent script is used to start the OpsCenter Agent service.

OPTIONS
Not applicable

NOTES
Enter the following command to start the OpsCenter Agent service on Windows:
INSTALL_PATH\OpsCenter\Agent\bin\startagent.bat

Enter the following command to start the OpsCenter Agent process on UNIX:
/opt/SYMCOpsCenterAgent/bin/startagent

Man pages for CLIs startdb

755

startdb
startdb This script starts the OpsCenter database.

SYNOPSIS
startdb

DESCRIPTION
The startdb script is used to start the OpsCenter database.

OPTIONS
Not applicable

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

To start the database server, enter the following command on UNIX:

/opt/SYMCOpsCenterServer/bin/startdb

756

Man pages for CLIs startgui

startgui
startgui This script is used to start the OpsCenter Web server service on UNIX

or Linux systems.

SYNOPSIS
startgui.sh

DESCRIPTION
The startgui script is used for starting the OpsCenter Web server service.

OPTIONS
Not applicable

NOTES
The following command starts the OpsCenter WebServer service on Windows:
INSTALL_PATH\OpsCenter\gui\bin\startgui.cmd

The following command starts the OpsCenter WebServer service on UNIX:

/opt/SYMCOpsCenterGUI/bin/startgui.sh

Man pages for CLIs startserver

757

startserver
startserver This script starts the OpsCenter Server.

SYNOPSIS
startserver

DESCRIPTION
The startserver script is used to start the OpsCenter Server.

OPTIONS
Not applicable

NOTES
Run the following command to start the OpsCenter Server on Windows:
INSTALL_PATH\OpsCenter\server\bin\startserver.bat

Run the following command to start the OpsCenter Server on UNIX:

/opt/SYMCOpsCenterServer/bin/startserver

758

Man pages for CLIs stopagent

stopagent
stopagent This script is used to stop the OpsCenter Agent.

SYNOPSIS
stopagent

DESCRIPTION
The stopagent script is used to stop the OpsCenter Agent on UNIX.

OPTIONS
Not applicable

NOTES
Run the following command to stop the OpsCenter Agent:
/opt/SYMCOpsCenterAgent/bin/stopagent

Man pages for CLIs stopdb

759

stopdb
stopdb This script is used to stop the OpsCenter database.

SYNOPSIS
stopdb

DESCRIPTION
The stopdb script is used to stop the OpsCenter database.

OPTIONS
Not applicable

NOTES
Run the following command to stop the OpsCenter database on Windows:
INSTALL_PATH\OpsCenter\server\bin\stopdb.bat

Run the following command to stop the OpsCenter database on UNIX:

/opt/SYMCOpsCenterServer/bin/stopdb

760

Man pages for CLIs stopgui

stopgui
stopgui used to stop the OpsCenter Web server service.

SYNOPSIS
stopgui.sh

DESCRIPTION
The stopgui script is used for stopping the OpsCenter Web server service.

OPTIONS
Not applicable

NOTES
The following command stops the OpsCenter Web server service on Windows:
INSTALL_PATH\OpsCenter\gui\bin\stopgui.cmd

The following command stops the OpsCenter Web server process on UNIX:
/opt/SYMCOpsCenterGUI/bin/stopgui.sh

Man pages for CLIs stopserver

761

stopserver
stopserver This script stops the OpsCenter Server.

SYNOPSIS
stopserver

DESCRIPTION
The stopserver script is used to stop the OpsCenter Server.

OPTIONS
Not applicable

NOTES
Run the following command to stop the OpsCenter Server on Windows:
INSTALL_PATH\OpsCenter\server\bin\stopserver.bat

Run the following command to stop the OpsCenter Server on UNIX:

/opt/SYMCOpsCenterServer/bin/stopserver

762

Man pages for CLIs stopserver

Appendix

Creating views using CSV, TSV, and XML files

This appendix includes the following topics:

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

764

Creating views using CSV, TSV, and XML files About using CSV, TSV, and XML files to create views

Example 4: Merging objects

About using CSV, TSV, and XML files to create views

You can use the Symantec OpsCenter Analytics console to create views. However, you may find it faster and more convenient to create the CSV, TSV, or XML files that describe the views that you want to create. This Appendix describes how you can create views using CSV, TSV, or XML files. You can then import, export, merge, or alias the CSV, TSV, or XML file into the OpsCenter database from the View Builder GUI or by using the view_exportimport script. See the Java View Builder help for information on how to import, export, merge, or alias a CSV, TSV, or XML file using the View Builder GUI. Information on how to import, export, merge, or alias a CSV, TSV, or XML file to Symantec OpsCenter Analytics by using the view_exportimport utility is available.

About creating CSV files

You can create views in Symantec OpsCenter Analytics by creating and importing the comma-separated values (CSV) file that describes the views. You can create the CSV files in a text editor, Excel etc. and save the file as <filename>.csv. Note that you can only create objects of type Generic when you create views using a CSV file. Note: You can export and import view structures using the CSV file. However, you cannot export or import attributes using a CSV file. A CSV file typically contains the following details:
First column View type View Type must be one of the following:

Master Server Client Policy File System Enterprise Vault Server Exchange Server Vault

Creating views using CSV, TSV, and XML files About creating CSV files

765

Second column Third column

Name of the view Level of the view (hierarchy). The third column and subsequent columns contain the name that you give to each level. You can have as many levels as you want, which must be specified in the third column or subsequent columns in the CSV file.

Last column

Host name

Note: The last column must be the host name. If the last column of a
row is not the host name, the specific row or entry is ignored and not considered.

The CSV file contains comma-separated values. Each row defines the hierarchy of one host. The following is the format of a sample CSV file. This CSV file contains only one level of view.
Client, View_Application, Oracle, client1 Client, View_Application, Oracle, client2 Client, View_Application, Sybase, client3

Figure D-1 shows the view that is created when you import the sample CSV file. Figure D-1 Sample view

The following is the format of a sample CSV file containing two levels of view.
Client, Client, Client, Client, View_Global, View_Global, View_Global, View_Global, India, Chennai, client1 India, Pune, client2 UK, London, client3 US, NYK, client4

766

Creating views using CSV, TSV, and XML files About creating TSV files

Figure D-2 shows the multi-level view that is created when you import the sample CSV file that contains two levels of view. Figure D-2 Sample multi-level view

Note: If you create a view using a CSV file that already exists in OpsCenter Analytics, the view gets deleted. You cannot modify an existing view by using a CSV file.

About creating TSV files

You can create views in Symantec OpsCenter Analytics by creating and importing the Tab-separated values (TSV) file that describes the views. You can create the TSV files in any text editor, Excel etc. and save the file as <filename>.tsv. Note that you can only create objects of type Generic when you create views using a TSV file. Note: You can export and import view structures using the TSV file. However, you cannot export or import attributes using a TSV file. A TSV file typically contains the following details:

Creating views using CSV, TSV, and XML files About creating TSV files

767

First column

View type View Type must be one of the following:

Master Server Client Policy File System Enterprise Vault Server Exchange Server Vault

Second column Third column

Name of the view Level of the view. The third column and subsequent columns contain the name that you give to each level. You can have as many levels as you want, which must be specified in the third column or subsequent columns in the TSV file.

Last column

Host name

Note: The last column must be the host name. If the last column of a
row is not the host name, the specific row or entry is ignored and not considered.

The TSV file contains tab-separated values. Each row defines the hierarchy of one host. The following is the format of a sample TSV file containing one level of view.
Client View_Application Oracle client1 Client View_Application Oracle client2 Client View_Application Sybase client3

Figure D-3 shows the view that is created when you import the sample TSV file.

768

Creating views using CSV, TSV, and XML files About creating TSV files

Figure D-3

Sample view

The following is the format of a sample TSV file containing two levels of view.
Client View_Global India Chennai client1 Client View_Global India Pune client2 Client View_Global UK London client3 Client View_Global US NYK client4

Figure D-4 shows the multi-level view that is created when you import the sample TSV file that contains two levels of view. Figure D-4 Sample multi-level view

Creating views using CSV, TSV, and XML files About creating XML files

769

Note: If you create a view using a TSV file that already exists in OpsCenter Analytics, the view gets deleted. You cannot modify an existing view by using a TSV file.

About creating XML files

You can create views in Symantec OpsCenter Analytics by creating and importing the XML files that describe the views. By using the XML API, you can import IT asset data and their relationships that you maintain through in-house or third-party systems (for example, Peregrine AssetCenter). The XML import capability enables you to import arbitrary groupings of master servers, clients, policies, Enterprise Vault servers, Exchange server, Vault, and file systems. For example, you can import the groupings that are defined around business units by using the XML import capability. Note: You can export and import view structures using the XML file. However, the attributes that are collected by data collectors like Network Name, OS etc. are not exported or imported. Only user-defined attributes like location, isTagged etc. can be exported or imported using an XML file. You can create user-defined attributes from the OpsCenter GUI (Settings > Configuration > Object Type). See About managing Object Types in OpsCenter on page 319. The following examples illustrate the practical use of OpsCenter Analytics XML import functionality. Example 1: You can use a spreadsheet to define Host A as the marketing host and Host B as the sales host. By importing the XML using the View Builder GUI or the view_exportimport utility, you can import the data in the spreadsheet, create a view using the imported data, and chargeback the services based on business units. Example 2: You can build a view of a chart of accounts that shows server ownership by company department for chargeback purposes. With large enterprises, the chart of accounts can easily exceed a thousand. Entering this data into Symantec OpsCenter Analytics is cumbersome and error prone. By importing the XML using the View Builder GUI or the view_exportimport utility, you can import this data from your local system. While importing the data into Symantec OpsCenter Analytics, you can continue with the maintenance of data in the local system.

770

Creating views using CSV, TSV, and XML files XML DTD structure

Importing data using XML is the best example of Symantec OpsCenter Analyticss open architecture that enables integration with other systems. See the following sections to know how you can create views in an XML file.

XML DTD structure

The XML DTD is constructed as follows:
<?xml version="1.0"?> <!-- Note : This DTD is provided for viewing the XML with tools like Microsoft's Internet Explorer. if it fails to work, the DTD should be replaced by the DTD provided with documentation. --> <!DOCTYPE application [ <!ELEMENT application (objects?,view*,user*,mergeitems*)> <!ATTLIST application version CDATA #REQUIRED> <!ELEMENT objects (object+)> <!ELEMENT view (node*,aliaslevels?)> <!ATTLIST view identifier CDATA #REQUIRED> <!ATTLIST view type CDATA #REQUIRED> <!ATTLIST view action (add|delete|update|declare) "declare"> <!ATTLIST view id ID #IMPLIED> <!ELEMENT object (attribute*)> <!ATTLIST object id ID #IMPLIED> <!ATTLIST object name CDATA #IMPLIED> <!ATTLIST object action (add|delete|update|declare) "declare"> <!ATTLIST object type CDATA #IMPLIED> <!ATTLIST object dbid CDATA #IMPLIED> <!ELEMENT node (object?,node*)> <!ATTLIST node id ID #IMPLIED> <!ATTLIST node action (add|delete|declare) "declare"> <!ATTLIST node object IDREF #IMPLIED> <!ATTLIST node parents IDREFS #IMPLIED> <!ELEMENT aliaslevels (level*)> <!ATTLIST aliaslevels action (add|update|delete|declare) "declare"> <!ELEMENT level EMPTY> <!ATTLIST level number CDATA #REQUIRED> <!ATTLIST level label CDATA #REQUIRED> <!ELEMENT mergeitems (mergeitem+)> <!ELEMENT mergeitem EMPTY> <!ATTLIST mergeitem toobject IDREF #IMPLIED> <!ATTLIST mergeitem fromobject IDREF #IMPLIED>

Creating views using CSV, TSV, and XML files DTD elements

771

<!ELEMENT attribute (name,value*)> <!ATTLIST attribute name CDATA #IMPLIED> <!ATTLIST attribute value CDATA #IMPLIED> <!ELEMENT name (#PCDATA)> <!ELEMENT value (#PCDATA)> ]>

DTD elements
The elements of the XML DTD are as follows:

See DTD <application> element on page 771. See DTD <objects> and <object> elements on page 771. See DTD <attribute> elements on page 773. See DTD <view> element on page 773. See DTD <node> elements on page 774. See DTD <aliaslevel> elements on page 774.

DTD <application> element

The <application> element is the root level tag that encloses rest of the XML definitions. This tag contains <objects> tag and zero or more other tags, namely <view> and <mergeitems> in this order.

DTD <objects> and <object> elements

The <objects> tag holds the definition of the objects to be acted on, and so contains a number of <object> tags. Each object tag represents a single asset in the Symantec OpsCenter Analytics configuration. Each object has the following properties that define it in the XML file:
id The ID of the object. This value is not the actual object ID but a unique value that identifies the object in the working XML. The actual name of the object. The action to be taken for the object. Add the object.

name action add

772

Creating views using CSV, TSV, and XML files DTD <objects> and <object> elements

delete

Delete the object. Note that for an object, delete operation does not delete the object from the OpsCenter database. For a view or node, the delete operation deletes the view or node but does not delete the related object from the OpsCenter database. Update the properties of the object. No action. You may need this object in XML at a later stage. In some cases, another object already present in the Symantec OpsCenter Analytics configuration may be required to take action using this object (for example, setting it as a master object for a newly defined object). To be able to do that, the object must first be declared in the XML. The type of the object. Currently, an object can be one of the following types:

update declare

type

MASTER_SERVER CLIENT POLICY MASTER_MEDIA MASTER_CLIENT MASTER_MEDIA_CLIENT MEDIA_CLIENT FILE_SYSTEM MEDIA_SERVER ENTERPRISE_VAULT_ SERVER EXCHANGE_SERVER VAULT

GENERIC

A generic object such as a hierarchical node in the View tree. A file system object. Host that acts as both media server and client. Host that is only a media server. A policy object

FILE_SYSTEM MEDIA_CLIENT MEDIA_SERVER POLICY

Creating views using CSV, TSV, and XML files DTD <attribute> elements

773

dbid

The database ID of the object. This field is optional and is written when the data is exported. It is very useful in cases where you want to update or declare objects. Because the dbid is an ID in the database, lookups are much faster. So, it is recommended to use the dbid to speed up the overall XML processing whenever possible. This ID is entirely database dependant and is created when the object is created. One cannot specify an object to have a specific dbid.

DTD <attribute> elements

Each object has a set of attributes that defines it in the Symantec OpsCenter Analytics configuration. These attributes are defined in the <attribute> tag. Each attribute tag can contain a <name> tag and multiple <value> tags. The <name> tag defines the name of the attribute and a <value> tag defines a value for it. The attribute tags can be defined in several ways, such as in the following example:
<attribute> <name>attrname</name> <value>attrvalue 1</value> </attribute>

Or:
<attribute name=attrname value=attrvalue/>

DTD <view> element

The <view > tag defines a view in the Symantec OpsCenter Analytics configuration. A view is a hierarchical association of objects. So, this tag contains multiple nested <node > tags that define the nodes of the tree. The tree tag contains the following properties:
identifier action add delete update The name of the view. The action to be taken for the tree. Create a new view. Delete an existing view. Update the view.

774

Creating views using CSV, TSV, and XML files DTD <node> elements

declare id type

No action. This property defines an already existing tree in the XML. Deprecated and no longer used. Specifies the view type

DTD <node> elements

A node can be viewed as a container that holds a single object. The same object can be contained in more than one node in the tree, but a node can contain only one object. The properties of nodes are as follows:
id object The unique identifier of the node in XML. The ID of the object that the node contains. This value is the ID given to that object in the working XML file and not the actual ID. There can be multiple parents for a node. In such a case, separte the parent node IDs by spaces in the XML. The node ID of this nodes parent node. The current node is added as a child to the specified parent node. This value is the ID given to the parent node in the working XML file and not the actual ID. The action to be taken for the node. Add the node to the tree. Delete the node. No action. You may need this node in XML at a later stage. In some cases, another node already present in the Symantec OpsCenter Analytics configuration may be required to take action using this node (for example, adding a child node). To use the node in XML as a parent for some other node, the node must first be declared in the XML.

parent

action add delete declare

DTD <aliaslevel> elements

In Symantec OpsCenter Analytics, you can set aliases or labels for levels in views. Using the <aliaslevel> element, you can specify names for view levels. A view contains number levels. By default, the levels are labeled Level 1, Level 2, and Level 3, which is not intuitive. To name the levels as per your requirements, you can use the <aliaslevel> element.
action The action to be taken for the aliaslevel.

Creating views using CSV, TSV, and XML files Examples of XML files

775

add update delete declare level number level label

Add the level number and level label. Update the level number and level label. Delete the level number and level label. Default action. Enter the level number like 1 or 2. Enter the label for the level.

Examples of XML files

You can create several types of XML files, including the following:

Add an object. See Example 1: Adding an object on page 775. Add a view. See Example 2: Adding a view on page 776. Update an object See Example 3: Updating an object on page 777. Merge two objects into a single object. See Example 4: Merging objects on page 778.

Example 1: Adding an object

Example 1, when imported into Symantec OpsCenter Analytics, adds the object Detroit under the MyMasterServers view. (The DTD header has been snipped.)
<application version="2.0"> <objects> <object id="o3" name="master.abc.domain.com" action="declare" type="MASTER_SERVER" dbid="58"> <attribute> <name>Location</name> <value>Illinois</value> </attribute> </object> <object id="o4" name="master1" action="declare" type="MEDIA_CLIENT" dbid="61" />

776

Creating views using CSV, TSV, and XML files Example 2: Adding a view

<object id="o5" name="dailybackuppolicy" action="declare" type="POLICY" dbid="62" /> <object id="o6" name="weeklybackuppolicy" action="declare" type="POLICY" dbid="63" /> <object id="o7" name="monthlybackuppolicy" action="declare" type="POLICY" dbid="64" /> </object> <object id="o10" name="Detroit" action="add" type="GENERIC" /> </objects> <view identifier="MyMasterServers" type="Master Server" action="update"> <node id="n268" action="add" object="o9" /> <node id="n269" action="add" object="o3" parents="n268" /> </view> </application>

Example 2: Adding a view

Example 2, when imported into Symantec OpsCenter Analytics, the TestMasterServers view is created with top-level branch as Chicago that contains a host object master1.abc.domain.com. (The DTD header has been snipped.)
<application version="2.0"> <objects> <object id="o3" name="master.abc.domain.com" action="declare" type="MASTER_SERVER" dbid="58"> <attribute> <name>Location</name> <value>Illinois</value> </attribute> </object> <object id="o4" name="master2" action="declare" type="MEDIA_CLIENT" dbid="61" /> <object id="o5" name="dailybackuppolicy" action="declare" type="POLICY" dbid="62" /> <object id="o6" name="weeklybackuppolicy" action="declare" type="POLICY" dbid="63" /> <object id="o7" name="monthlybackuppolicy" action="declare" type="POLICY" dbid="64" /> <object id="o9" name="Illinois" action="declare" type="GENERIC" dbid="66">

Creating views using CSV, TSV, and XML files Example 3: Updating an object

777

<attribute> <name>Name</name> <value>Illinois</value> </attribute> </object> <object id="o10" name="Chicago" action="declare" type="GENERIC" dbid="67"> <attribute> <name>Name</name> <value>Chicago</value> </attribute> </object> </objects> <view identifier="MyMasterServers" type="Master Server" action="update"> <node id="n268" action="add" object="o9" /> <node id="n269" action="add" object="o3" parents="n268" /> </view> <view identifier="TestMasterServers" type="Master Server" action="add"> <node id="n271" action="add" object="o10" /> <node id="n272" action="add" object="o3" parents="n271" /> </view> </application>

Example 3: Updating an object

Example 3, when imported into Symantec OpsCenter Analytics, updates the Location attribute of master1.abc.domain.com (to Illinois). The Name attribute of Chicago object is also updated (to Chicago). (The DTD header has been snipped.)
<application version="2.0"> <objects> <object id="o3" name="master.abc.domain.com" action="update" type="MASTER_SERVER" dbid="58"> <attribute> <name>Location</name> <value>Illinois</value> </attribute> </object> <object id="o4" name="master3" action="declare"

778

Creating views using CSV, TSV, and XML files Example 4: Merging objects

type="MEDIA_CLIENT" dbid="61" /> <object id="o5" name="dailybackuppolicy" action="declare" type="POLICY" dbid="62" /> <object id="o6" name="weeklybackuppolicy" action="declare" type="POLICY" dbid="63" /> <object id="o7" name="monthlybackuppolicy" action="declare" type="POLICY" dbid="64" /> <object id="o9" name="Illinois" action="declare" type="GENERIC" dbid="66"> <attribute> <name>Name</name> <value>Illinois</value> </attribute> </object> <object id="o10" name="Chicago" action="update" type="GENERIC" dbid="67"> <attribute> <name>Name</name> <value>Chicago</value> </attribute> </object> </objects> <view identifier="MyMasterServers" type="Master Server" action="update"> <node id="n268" action="add" object="o9" /> <node id="n269" action="add" object="o3" parents="n268" /> </view> </application>

Example 4: Merging objects

Example 4, when imported into Symantec OpsCenter Analytics, merges object o2 into the object o1. Objects o1 and o2 represent the same host. One has a host name of hostA.veritas.com and the other has the host name as hostXYZ.somedomain.veritas.com. While merging object o2 into object o1, you can specify hostXYZ.somedomain.veritas.com as an alias for object o1. After merging object o2, it is deleted and only object o1 remains. In Example 4, a host object has the hostname hostA.veritas.com which also goes by the name hostXYZ.somedomain.veritas.com. The XML export of this object looks like the following: (The DTD header has been snipped.)

Creating views using CSV, TSV, and XML files Example 4: Merging objects

779

<object id="o1" action="declare" type="Host" dbid="50"> </object>

This example has another host object whose host name is hostA and whose XML export is as follows:
<object id="o2" action="declare" type="Host" dbid="70"> </object>

Now, whenever a particular Symantec OpsCenter Analytics Agent refers to a host as hostA, the Symantec OpsCenter Analytics Server identifies the object since one of its host names matches this object. After this object update, you can merge the two hosts with the following syntax:
<mergeitems> <mergeitem toobject = "o1" fromobject = "o2"/> </mergeitems>

Merging of two hosts moves all data from the hostA object to the newly updated object and deletes the hostA object.

780

Creating views using CSV, TSV, and XML files Example 4: Merging objects

Glossary

Administrator Console application

See CommandCentral Service View Builder. A program or group of programs designed to perform a specific task. Oracle Database and Veritas NetBackup are examples of applications. A Server component that manages policies associated with objects on the storage network. A policy associates certain sets of conditions with storage resources and defines actions to be taken when these conditions are detected. The Alert Manager is seamlessly integrated with the CommandCentral product offerings so that Console users can monitor, define, and modify policies. Data collector is a part of Symantec OpsCenter Agent that collects data from various products. A notification that indicates when an action, such as an alert or a change in state, has occurred for one or more objects on the storage network. In CommandCentral Service, a Console area in which to display and run custom reports saved by the user. A component of the Veritas Security Services (VxSS) that is used by the and runtime libraries that enables users to log on to multiple Veritas products with one logon.

CommandCentral Alert Manager

Data Collector

event

My Reports

VAS (Veritas

Authentication Service) CommandCentral offerings to provide user authentication. VAS is a set of processes

VxPBX (Veritas Private Branch Exchange)

A common Veritas component that uses socket passing to reduce the number of ports required to be open across a firewall. VxPBX uses a paradigm similar to that of a telephone switchboard in which calls placed to a switchboard are redirected to a known extension. In the PBX exchange, client connections sent to the exchange's port are redirected to an extension associated with the CommandCentral Service Management Server. A graphical user interface that displays reports and other information for users of CommandCentral Service through a standard Web browser. The Console provides a central point to manage cost analysis and chargeback for services, managing workflow, displaying and managing reports, and other tasks. A database, residing on the Server, that gathers data related to performance and monitoring, reports, alarms, service requests, and the SAN Access Layer (SAL). A Sybase ASA (Adaptive Server Anywhere) database management system, the Server database is installed silently when you install CommandCentral Service.

CommandCentral Console

CommandCentral Database

782

Symantec OpsCenter Glossary

CommandCentral Service

A product offering that tracks IT effectiveness by providing complete business-level reporting of resource utilization, costs, and service level delivery. CommandCentral Service also helps enable business customers ensure that their application performance and availability requirements are met at the lowest cost. The licensed version of OpsCenter is called Symantec OpsCenter Analytics. Symantec OpsCenter Analytics lets you do advanced business-level reporting. The part of CommandCentral Service that collects information from discoverable applications residing on remote host systems, such as Veritas NetBackup, Veritas Backup Exec, and EMC Legato Networker. CommandCentral Service formats the information collected from these applications and displays it through the CommandCentral Console. The portion of the CommandCentral Service product offering that resides on the primary host. A Flash-based application in which an administrator creates, modifies, and manages access to the object views that users see in the CommandCentral Console. (An earlier, Java-based version of this application was known as the Administrator Console in earlier releases of CommandCentral Service.) See also object view. Symantec OpsCenter views are logical groups of IT assets (hosts or file systems) organized in a hierarchical manner. You can create views in Java View Builder and make them available in the Symantec OpsCenter console. The following view details appear in the Symantec OpsCenter console.

Symantec OpsCenter Analytics CommandCentral Service Agent

CommandCentral Service Management Server CommandCentral Service View Builder

Views

Index

A
about Symantec OpsCenter 23 about Symantec OpsCenter Analytics 24 access OpsCenter console 41 ActiveX 40 add master server 377, 381, 385 NetBackup 7.0 master server 377 add email recipient options 333 add email recipient options 333 Add Master Server options 381 add SNMP trap recipient options 335 add SNMP trap recipient options 335 adding existing user 327 new user 327 adding users 321 Agent deploying 95 overview 35 agent delete 357 modify 356 Agent deployment 95 Agent options 354 agent.conf file 38 alert policies alert conditions 501 alerts filtering by type 487 responding to 488 archive data 393

breakup jobs 370371 viewing 370 Breakup Jobs option 366 business planning 27

C
capacity license 536 Change Job Priority dialog box options 441 Change Job Priority dialog box options 441 changeDbPassword 742 changeVxATProperties 744 changing AT parameters 272 chargeback cost variables 340, 342 formulae 343 modeling 344 cluster 233, 248 installing OpsCenter server UNIX 252 Windows 241, 244 limitations UNIX 249 Windows 237 OpsCenter server Windows 237 preinstallation checklist 251 all VCS cluster configurations 251 VxVM 252 prerequisites UNIX 249 Windows 238 supported OS 233 supported solutions 233 uninstalling OpsCenter server UNIX 257 Windows 247 color use in OpsCenter 70 compliance reporting 27

B
backing up OpsCenter database 279 Backup Exec 388 bookmarks using with OpsCenter 77

784

Index

configure session timeout interval 54 configure SMTP 311 configure ThreatCon feature 312 configurePorts 745 configuring Enterprise Vault data collector 403 connected master server state 376 Content pane enlarging 69 Summary and Hierarchical views 67 control OpsCenter logging on UNIX 296 on Windows 295 controlling OpsCenter services and processes 264 copy user profile options 318 copy user profile options 318 copying user profile 317 cost formulae 343 cost estimation 344 options 345 cost estimation options 345 cost variable options 339 cost variable options 339 costs variables 340 Create Agent options 356 create alert policy 509 Create Time Schedule options 610 creating cost formulae 343 cost variables 340 custom report 591 custom SQL query 592 email recipients 333 SNMP trap recipients 334 views 415 currency settings options 338 currency settings options 338 custom reports 582 custom SQL query 582 customizing alert settings 576

D
data collection 379 data collection status 370, 372 view 373 Data Collection view 363 Data Collector configuring 358, 361 deleting 361 data collector Backup Exec 388 Data Collector configuration 360 Data Collector status viewing 357 Data Collector Wizard 359 Data migration from NOM to OpsCenter 169 from VBR to OpsCenter 186 data purge configure 309 restore NOM or VBR purge settings after upgrade 310 database see (OpsCenter database) 267 dbbackup 746 dbdefrag 747 deduplication 389 defining cost formulae 343 cost variables 340 delete master server 387 Deleting user group 330 deleting alert recipients 336 cost formulae 343 views 416 deleting user 327 dependency of OpsCenter services 266 deployment analysis 536 deployment mode multi domain 398 single domain 398 standalone mode 398 disable security warnings on Mozilla 42 on Mozilla and IE 43 documentation for Sybase 267

Index

785

documentation (continued) HTTP and HTTPS ports 289 NBSL 92 NetBackup 39 SymcOpsCenterWebServer 80 VxUL 80

E
edit master server 386 Edit Agent options 356 edit currency list options 339 edit currency list options 339 Edit Time Schedule options 610 editing currency list 338 editing user profile 327 editing users 321 email options 331 report 589 email options 331 email recipients creating 333 EMC data collector 406 EMC Networker 406 Enterprise Vault 393 data types 393 versions supported 396 Enterprise Vault data collector 403 data collection checklist 404 deployment scenarios 396 exporting report 588

Guided Recovery (continued) metadata 546, 553 Performing a cloning operation 547 Post-clone operations 552 Pre-clone check screen 552 Pre-operation checks 547 Select Control File Backup screen 549 Select Destination Parameters screen 551 Select Master Server screen 549 Select Source Database screen 549 Selection summary screen 552 Troubleshooting 553

H
heap size adjusting 221 host alias adding 313 viewing 313

I
IBM Tivoli Storage Manager 405 icons for managed server status 70 install AT UNIX 250 Windows 239 clustering. See cluster OpsCenter DVD 85 install and upgrade checklist 101 install OpsCenter on UNIX 111 on Windows 107 Installing OpsCenter 106

F
file formats 589 firewall considerations 284 firewalls Symantec Private Branch Exchange 33 floating-point math and OpsCenter 228

J
JavaScript 40 Jobs List View options 434 Jobs List View options 434 jre (Java Run Time Environment) 80

G
getting started with typical OpsCenter tasks 76 Guided Recovery 545 Destination host and login screen 550 Job Details screen 552

L
license viewing 307 license keys 82 adding 308 deleting 308

786

Index

license keys (continued) viewing 308 license report issues 543 licensed OpsCenter features 83 licenses adding 307 managing 307 licensing model 81 licensing page 541 log files on UNIX servers 298 on Windows servers 296 logging in to OpsCenter 51 out of OpsCenter 54

monitor views (continued) monitoring devices 472 monitoring hosts 480 monitoring jobs 433434, 441 monitoring media 462 monitoring policies 453 monitoring services 451 Mozilla Firefox 41 MS SQL Server host 398 MS SQL Server JDBC driver 402 multi-domain deployment mode 400 My Dashboard options 597 My Dashboard tab 596 My Reports tab 593

M
Manage Folders options 599 Manage views controlling scope 498 manage devices 523 manage storage 518 managed master server considerations 91 managed server icons 70 Management Information Base (MIB) 559 managing folders 599 manual upgrade on a new UNIX system 206 on a new Windows system 201 master server 379 add 377 details 372 master server states 376 Microsoft Internet Explorer 41 Microsoft SQL Server versions supported 396 modeling chargeback 344 modifying alert recipients 336 cost formulae 343 cost variables 342 report export location 318 views 415 Monitor views controlling scope 425 monitor views monitoring alerts 484

N
nbproxy process 266 NetBackup 7.0 master server add 377 NetBackup Data Collection concept 364 NetBackup data collection adding a master server 377 deleting a master server 387 editing a master server 386 enabling or disabling data collection 387 managed master server versions 372 supported data types and collection status 374 NetBackup options 362 NetBackup PureDisk data collector configuring 391 NetBackup Service Layer (NBSL) 92, 290, 364 Network Address Translation (NAT) network considerations 91 NOM upgrade considerations 144 not connected master server state 376

O
object merger options 315 object type add 319 add attribute 320 delete 320 delete attribute 321 modify 320 options 319

Index

787

object type options 319 object types 319 objects (hosts) merging 315 opsadmin 748 OpsCenter adjusting heap size 221 Sybase cache size 226 and floating-point math 228 color use 70 database 93 installing UNIX 111 Windows 107 sanity check after installing 211 sizing 92 status bar 69 store database and logs on separate disk 272 Sybase database used 81 tasks performed on startup 213 uninstalling UNIX 231 Windows 231 OpsCenter 7.1 new features 28 OpsCenter alerts about alert policies 499 alert conditions 501 creating alert policy 501 managing alert policy 517 understanding alert counts 516 OpsCenter architecture database 34 Server and Authentication Service 35 OpsCenter back up and restore procedures 278 OpsCenter console alert summary pane 66 content pane 67 description 58 quick links 66 tabs and subtabs 60 ThreatCon pane 65 title bar 59 View pane 61 OpsCenter context-sensitive help locating 39 OpsCenter database back up using backupDB script 278

OpsCenter database (continued) backing up 279 restoring 281 OpsCenter database password file 281 OpsCenter database utilities change database administrator password 268 defragment OpsCenter databases 270 OpsCenter DVD layout 85 OpsCenter installation hardware requirements 92 install checklist 101 master server considerations 91 Operating System requirements 86 supported backup and archive products 89, 351 web browser considerations 40 OpsCenter post-installation starting to use OpsCenter 212 OpsCenter processes on UNIX 261 OpsCenter reports 579 OpsCenter Server 33 Authentication Service 35 OpsCenter server scripts on Windows and UNIX 263 OpsCenter services on Microsoft Windows 260 OpsCenter start-up tasks 213 OpsCenter system requirements see OpsCenter 92 OpsCenter upgrade procedures 136 OpsCenter user profiles 280 OpsCenter View Builder 38 OpsCenter views managing 414 overview 409, 411 opsCenterAgentSupport 750 opsCenterSupport 751 originator ID 294 OS considerations 88

P
partially connected master server state 376 password changing 307 PBX 33 PDOS 389 performance tuning 213

788

Index

policy filtering by type 456 port numbers backup and archive products 287 HTTP 288 HTTPS 288 key OpsCenter components 284 ports Symantec Private Branch Exchange 33 product ID 294

Q
quick links minimizing 66 quick start for OpsCenter tasks 76

R
refresh OpsCenter console 61 report export 318 report export location options 318 report export location options 318 report schedules 604 report template 612 report templates 581 reports Scheduled Jobs 627 restoring OpsCenter 281 runstoredquery 753

S
saving report 588 Scheduled Jobs reports 627 All Jobs report 630 scheduled jobs reports Job Count Details-Scheduled Vs Actual report 629 Job Count Within Backup Window report 628 Job Count-Scheduled Vs Actual report 628 schedules 601 Schedules options 603 scripts runstoredquery 753 server.conf file 227 services controlling 452

services (continued) filtering by type 452 setting default currency 337 Simple Network Management Protocol (SNMP) 558 configuring community name 574 configuring SNMP version 575 SNMP traps 559 supported SNMP versions 559 Single Instance Storage SIS 389 single-domain deployment mode 399 SLP reports about 657 SLP Backlog report 665 SLP Status by Client report 670 SLP Status by Destinations report 684 SLP Status by Image report 675 SLP Status by SLP report 666 SLP Status report 660 SLp reports SLP Status by Image Copy report 680 SMTP server options 311 options 311 SNMP port 290 SNMP trap recipient options 332 SNMP trap recipient options 332 SNMP trap recipients creating 334 software components used by OpsCenter 79 standalone deployment mode 400 standard reports descriptions 636 start-up tasks OpsCenter server 213 startagent 754 startdb 755 startgui 756 starting runstoredquery 753 startserver 757 status icons 70 stopagent 758 stopdb 759 stopgui 760 stopserver 761 supported backup and archive products 351 supported backup products 27

Index

789

supported platforms 86 supported upgrade paths 95 Sybase cache size adjusting 226 Symantec Java Web Server (SymcOpsCenterWebServer) 80 Symantec OpsCenter difference between Symantec OpsCenter Analytics 83 Symantec OpsCenter Analytics difference between Symantec OpsCenter 83 Symantec OpsCenter Analytics and Symantec OpsCenter 81 Symantec OpsCenter Analytics XML DTD 770 DTD elements 771 Symantec OpsCenter AnalyticsXML example files 775 Symantec Private Branch Exchange 33 port number configuration 80 Symantec Private Branch Exchange (PBX) 80 port number configuration 382 Symantec Product Authentication Service installing UNIX 250 overview 35 shared component 80 Windows installing 239

troubleshooting (continued) OpsCenter server issues 55 support script in OpsCenter 291 VBR database inconsistency issues 168 TSM data collector 405 tuning OpsCenter for performance 213

U
unified logging (VxUL) 294 uninstalling OpsCenter UNIX 231 OpsCenter on Windows 231 UNIX installing OpsCenter 111 upgrading OpsCenter 7.0 to OpsCenter 7.1 141 upgrades to OpsCenter default data purge settings 310 use NOM or VBR purge settings 310 upgrading OpsCenter 7.0 to OpsCenter 7.1 UNIX 141 Windows 137 upgrading to OpsCenter from NOM on UNIX 148 from NOM on Windows 145 from VBR on UNIX 161 from VBR on Windows 155 user creating multi-domain deployment mode 400 single-domain deployment mode 399 standalone deployment mode 400 user access rights 322 user groups creating 329 options 329 user groups options 329 user preferences options 304 user preferences options 304 user profiles viewing 326 using an old NOM or VBR installation 229

T
tables in OpsCenter applying filters 75 creating custom filters 74 customizing 71 selecting rows 74 using filters 74 viewing hidden columns 71 viewing multiple pages 73 tape library modifying 316 ThreatCon options 313 ThreatCon options 313 time schedule 610 tool tips 70 troubleshooting accessing OpsCenter 45 OpsCenter console logon issues 52

790

Index

V
VBR upgrade considerations 168 Veritas Cluster Server (VCS) for UNIX/Linux preinstallation checklist 251 Veritas NetBackup PureDisk PDOS 389 Veritas Unified Logging (VxUL) 80 log files 294 originator IDs used by OpsCenter 294 view accessing 413 level 413 view NOM data migration status 180 view OpsCenter alerts using HP OV NNM 578 using HP OV NNM 7.50/7.51 on Windows 578 using SCOM 2007 577 View pane making selections 63 using 61 view VBR data migration status 195 viewing email recipients 331 viewing alerts using List View 485 using Summary View 491 views view type 412 Views options 411 visual keys in the OpsCenter console 70

X
XML DTD 770 examples for importing 775 importing 770

W
web browser book marks 77 pop-up blockers 40 support 41 UTF-8 40 Windows installing OpsCenter 107 uninstalling OpsCenter 231 upgrading OpsCenter 7.0 to OpsCenter 7.1 137