OpsCenter Install

From Spaldam's Wiki
Jump to navigationJump to search
World History Wiki is Brought to you by:
S.J.'s Adventures

These documents are for entertainment purposes only. Use at your own risk. This site is in no way affiliated with Veritas or NetBackup, and any trademarks are those of their respective companies.

If you need assistance with anything NetBackup and/or Disaster Recovery related, You can find me on linkedIn.

Helpful Resources[edit]



  • Check the Hardware Comparability list for compatible hardware
  • Performance Tuning recommendations from Veritas for version 7.6 are TBD at the time of this writing, but here are a few ideas I've learned working with OpsCenter for many years:
    • If you have small environment, virtualizing the OpsCenter server is very doable, but it may run slower then desired
    • The Sybase DB will only run as fast as the disk it is installed on. I recommend high performance SAN disk or a Flash drive (for VM's use RDMs or pass-through LUNs).
    • Other considerations are the number and size of the reports that get run; the more frequent and larger the reports, the more RAM and CPU power you need.
      • I've seen small environments - 1 master, a few thousand jobs a day, and a few reports per day - use a VM with 2 CPU 8 Gig RAM work okay with a little slowness.
      • I've seen large environments - 6 masters, tens of thousands of jobs a day, and a dozen or more reports a day - use a physical server with 8 CPUs and 32 Gig RAM run very slow.


  • Check the OS Compatibility list for compatible OS's to install on.
    • The easiest and most function OS in my experience is Windows 2008 x64 or newer; especially if you require AD authentication/integration.
    • Can also be installed on Linux, but for AD integration you'll still need to install the Authentication pieces on a Windows server.


  • Get your licensing information together; especially your Serial Number for downloading.
    • Identify the optional OpsCenter Analytics license key if you purchased one.
  • Download the software and copy OpsCenter_7.6.0.1_Win.zip (or OpsCenter_7.6.0.1_Unix.tar.gz) to the server OpsCenter is to be installed on.
    • Make sure there is sufficient disk space, and appropriate network connection to your OpsCenter server.
    • Identify any special Filesystems that are to be used for the OpsCenter installation location.
    • Extract the ".zip" (or ".tar.gz") installation bundle to a temporary location.


Install Binaries[edit]

Image - Browser.exe
  1. Locate and run the "Browser.exe" from the instillation binaries.
    • On the resulting menu, select "Installation"
    • Then click on "OpsCenter Server Installation"
  2. Click "Next" on the "Welcome Page".
  3. Underneath the "User Agreement" You'll need to put a check mark in the box next to "Agree with Veritas Software License Agreement." (or don't it's up to you). The install will no allow you to continue if you don't.
    • Participation in the "NetBackup Product Improvement Program" is entirely optional.
    • Click "Next" when you have made your selections.
  4. On the "Instillation Choice" window I recommend selecting "Custom". Even if you don't change any settings, you will at least learn where your are installing the file to.
    • If you are on a clustered environment, you will need to select "Install a Clustered OpsCenter Server", but that is beyond the scope of this document.
    • Click "Next" once you have your selections made.
      Image - Location
  5. On the "Location Selection" window (see image on right) you can see the default installation location, and update it to meet your needs.
    • In this example we are putting in on the "F:" drive because it is using a "Fusion Card" that allows SAN disk to be connected with a buffering Flash Disk on the front end for high performance.
    • click "Next" once you have made any necessary modifications to the instillation location.
    • If the Directory doesn't currently exist (which it most likely doesn't), you will need to click "Yes" on a resulting dialog window to confirm the location.
  6. The OpsCenter Installation will now prompt you for the optional License Keys.
  7. The Last step before installation actually starts is to verify all the options you selected.
    • Review your selections. This is your last chance to click on "Back" to change any of your selections.
    • It's also a good idea to make sure the box next to "Save summary to:" has a check in it, and the location is one you can remember. If you run into issues during the install, you'll need this log for troubleshooting.
      Image - Installation Complete
    • If everything is correct, click on "Install".
  8. Monitor the installation to make sure no errors appear.
    • Once complete you should get a window that says "Installation Complete'" with some check boxes, and a "Finish" button.
    • Having the check box next to "Launch OpsCenter user interface" will allow you to go straight into the initial configuration.
    • NOTE: Don't forget to close the "Browser" window, or explore the content within it more if desired.

Install Patch[edit]

Apply the latest patch

See: http://www.veritas.com/docs/000076576


  1. The first time you launch the OpsCenter User Interface (If you don't see the Icon, just point a web-browser to the OpsCenter Server) your web-browser will likely complain about security issues with the web-page. This is because OpsCenter requires using ssl (or https) to prevent snooping of passwords and backup data that will provide details about the infrastructure.
    Image - Security Certificate Error
  2. The first page to pop up on the OpsCenter web interface prompts you to log-in.
    This page also contains a number of other useful links and information.
    Image - OpsCenter Log-in Page
    • After a fresh install only one account exists:
      User: admin
      Password: password
      Domain: OpsCenterUsers(vx)
    • When you first log-in it will require that you change the default admin password.
    • After changing the password, it will prompt you to log-in again with the new password.
  3. The first time you successfully log-in to OpsCenter it will give you a list of items to configure.
    Image - Recommended Config Steps
    • This is a good list of items to take care of, but the most important is to create a user accounts other then the default "admin" account with Security Admin privileges.
      • If you forget the Admin password, you'll want a secondary account that you can get in through to change the Admin password.
      • Each additional user, should get their own log-in and password. Sharing the Administrator log-in is a poor security practice.
    • It's also a good idea to look at the layout and familiarize yourself with the top level menu which includes links to:
      Home, Monitor, Manage, Reports, Search & Hold, Settings
    • The most important of these right now is the "Settings" tab.
  4. The Settings tab allow for configuring the basic functionality of OpsCenter including:
    Image - OpsCenter Users Menu
    1. User Preferences (for the currently logged in user)
    2. Configuration (for all the nitty gritty technical configuration options)
    3. Views (A nice feature of OpsCenter to help you organize different types of clients and/or servers)
    4. Users (Where Security Administrators go to setup, modify, and delete OpsCenter users)
      For more details see "To add a new user to OpsCenter" section, starting on page 194, of the OpsCenter Administrator's Guide.
      Also see "OpsCenter user roles" on page 190.
    5. Recipients (Allows you to configure E-mail and SNMP recipients for sending reports and alerts to)
    6. Chargeback (in case you need to charge - or just report on - other departments for how much data is being protected)
    • After configuring an additional user(s) other then the default "admin" (preferably with Security Administrator privileges to make sure you can change the admin password if necessary) the most important section to focus on is in the "Configuration" tab.
      Image - OpsCenter Configuration Menu
  5. Under "Settings -> Configuration" You'll find the real meat of OpsCenter's configuration options.
    • The most important things to get setup as soon as possible are on these Tabs:
    1. NetBackup (to add master servers for OpsCenter to start monitoring and collecting data from -- Servers running older versions may require installing an Agent).
    2. Data Purge (to make sure it's keeping data long enough to meet your needs)
    3. SMTP Server (so you can send e-mailed reports)

settings", starting on page 243, of the OpsCenter Administrator's Guide].

Post Installation Task[edit]


Optionally, you can also install the View Builder if you feel it would be useful. It's usually easiest, but not necessary, to install it on the same server as the OpsCenter Server.

Also be sure to review the OpsCenter performance Tuning Guide which describes the following tuning options:

  • Install the OpsCenter database on a drive that is different from where OpsCenter server software and operating system is installed (See Installation Instructions).
  • Install the OpsCenter log files on a drive that is different from where OpsCenter server software and operating system is installed. This type of installs should be done only if the logging level is greater than 1.
    INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a –p 58330 -o 148 -s LogDirectory="New_log_directory_location"
    INSTALL_PATH\OpsCenter\Agent\bin\vxlogcfg -a –p 58330 -o 146 -s LogDirectory="New_log_directory_location"
    INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a –p 58330 -o 147 -s LogDirectory="New_log_directory_location"
  • Veritas recommends that you de-fragment the OpsCenter database periodically. You must perform de-fragmentation once a month.
  • Increase the heap size of the OpsCenter server depending on the RAM load. See “Adjusting the default heap size for the OpsCenter server service” on page 23.
  • Increase the heap size of the OpsCenter web server service depending on the RAM and the database size. See “Adjusting the default heap size for the OpsCenter web server service” on page 24.
  • Increase the database cache size depending on the RAM and the database size. See “Adjusting the OpsCenter database service cache size” on page 27.
  • Create report schedules such that the email or export happens in system-idle time during which OpsCenter is not accessed frequently.
  • Purge the OpsCenter data periodically.


  • Configure Users
  • Configure Views
  • Configure Recipients
    • Report Emails
    • SNMP traps
  • etc...


Two Example reports to use are configured this way:

Weekly Success Rate[edit]

  1. Reports -> Report Templates
  2. Report Templates \ Backup Reports \ Status & Success Rate Reports \ Success Rate Reports \ Advanced Success Rate
  3. Edit Report
  4. Relative TimeFrame: “Previous 7 days”
    Time Frame Group by: 10 days
    Filter by Job: Job Type = “Backup”, “Backup From Snapshot”
  5. Report on: Master Server
    Description: [left at default]
    Display Unit: TB
    Rows Per Page: 100
  6. Report name: “Weekly Success Rate”
    Description: “List of Success vs. Failure and Percentage for last week”
    Folder: “Public Reports\Team Reports\Scheduled Team Reports”

Weekly Success Rate Scheduling[edit]

  1. Reports -> Schedules -> "Add"
  2. Report Schedule Name: “Weekly HTML Reports”
    Format: “HTML”
  3. Create new Time Schedule
  4. Schedule Name: “Monday 9am”
    Schedule Time: “09:30”
    Schedule Patter: Weekly
    Recur every: “1 Weeks” on “Monday”
    Starting date: “Today”
    No End date
  5. Email To: TEAM-Email-Address@domain.com
    Subject: Weekly OpsCenter HTML Reports
    Message: These are the Daily Ops Center HTML Email Reports
  6. Select “Weekly Success Rate” Report and any others to send with this report.
  7. No conditions

Weekly STU Load Report[edit]

  1. Reports -> Report Template
  2. Report Template \ Workload Analyzer Reports \ Job Throughput Workload Analyzer
  3. Edit Report
  4. Relative TimeFrame: “Previous 1 Weeks”
    No Filters
  5. Report On: “Storage Unit Name”.
    Sort Order: “None”
    Color Code Ranges: 100, 5000, 10000
    Description: [Default]
  6. Report Name: “Weekly STU Load”
    Description: “Graph showing STU Loads for previous week”
    Folder: “Public Reports \ Team Reports \ Scheduled Team Reports”

Add to Existing Schedule[edit]

  1. Reports -> Schedules
  2. Select “Weekly HTML Reports”
  3. Edit
  4. Leave “Details” unchanged
  5. Leave Schedule unchanged
  6. Leave Email settings unchanged
  7. Add check next to “Weekly STU Load” Report Name.
  8. Click on “Save”, then “Finish”.


All alerts that are available for configuration can be seen by going to:

  • "Manage" tab
  • "Alerts Policies" sub-tab
  • Click on "Add" button.

Each Alert has different parameters that can be configured as you "Add" them to make them active.


Periodic maintenance of the OpsCenter database is needed. The OpsCenter Administrator's Guide on pages ??? provides commands used to maintain and protect the OpsCenter database.

Database Backup[edit]

Regular backups should be performed

The "dbbackup" script is used for backing up the OpsCenter database.

dbbackup <DB_BACKUP_DIR> [-v | -restore]

Where "DB_BACKUP_DIR" is the directory where to backup to or restore from. The "-v" switch tells the script to validate the database after backup, and "-restore" tells the script you are trying to restore the database.

For example:


INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat D:\OpsCenter_backups\20140421\


<INSTALL_PATH>/SYMCOpsCenterServer/bin/dbbackup.sh /nbu/OpsCenter_backups\20140421\

Database De-fragmentation[edit]

The "dbdefrag" script is used to de-fragment the OpsCenter database. It's a good idea to de-fragment the database on a regular monthly schedule. This does require taking OpsCenter off-line.






See The OpsCenter Administrator's Guide starting on page 737


For settings to take affect, OpsCenter must be stopped, and then started again after edits are made.

From the Command-line navigate to '<InstallPath>/opscenter/server/bin/', and type:

opsadmin stop

To start, run:

opsadmin start

Memory usage[edit]

Navigate to the OpsCenter installation directory:

Windows C:\Program Files\Veritas\OpsCenter\server\config
UNIX <INSTALL_PATH>/SYMCOpsCenterServer/config

Open server.conf in a text editor, and look for the following entry:

-ch 8G

Depending on the amount of memory on the server size of the environment being monitored, you can increase this to as much as 16-24 GB of RAM, and possibly more.

-ch 24G

For the Java GUI Maximum Memory, Navigate to OpsCenter\gui\bin, open OpsCenterGUIService.xml, and look for:


Extending this to 4096 will allow the Java console to request up to 4 GB of RAM

Report Rows[edit]

To configure the maximum number of rows for export Navigate to the following location:

Windows C:\Program Files\Veritas\OpsCenter\server\config
UNIX <INSTALL_PATH>/SYMCOpsCenterServer/config

Edit the report.conf file

You may want to export all the rows or you may want to increase or decrease the maximum value. Note that if you export all rows or increase the number of rows, exporting a report may take time when there are a large number of rows.

To export all the rows, you can either comment out report.schedule.max.tabular.rows parameter using two forward slashes at the beginning of the line, or specify any value less than or equal to -1

Alternately you can change the value to the maximum number of rows you want to allow the report to generate.

Back to NetBackup