Veritas NetBackup™ OpsCenter Performance and Tuning Guide

Last Published:
Product(s): NetBackup (8.1.2, 8.1.1, 8.1)
  1. Overview
    1.  
      Purpose of the guide
    2.  
      Disclaimer
  2. About OpsCenter configuration
    1.  
      OpsCenter Server configuration
    2. About OpsCenter Server on a virtual machine
      1.  
        Physical versus virtual configuration for OpsCenter Server
      2.  
        Guidelines on the OpsCenter VM parameters
      3.  
        About VM settings and % gains during OpsCenter report generation
    3.  
      OpsCenter database configuration
    4.  
      OpsCenter services
  3. About OpsCenter performance and tuning
    1.  
      Sizing considerations
    2.  
      Sizing guidelines
    3. About tuning OpsCenter for increased performance
      1.  
        About performance tuning guidelines
      2.  
        About adding NetBackup Master Servers to OpsCenter
      3.  
        About using a web browser to access OpsCenter
      4. About saving the OpsCenter log files on a different drive
        1.  
          Checking the debug level of logs
        2.  
          Saving the log files to a different location on Windows
        3.  
          Saving the log files to a different location on UNIX
      5. About adjusting the heap size or cache size for OpsCenter services
        1.  
          Adjusting the default heap size for the OpsCenter server service
        2.  
          Adjusting the default heap size for the OpsCenter web server service
        3.  
          Adjusting the default heap size for the OpsCenter Agent service
        4.  
          Adjusting the OpsCenter database service cache size
      6. About OpsCenter database defragmentation
        1.  
          Checking the disk fragment count
        2.  
          About allocating more memory before database defragmentation
        3.  
          Defragmenting the OpsCenter database
      7.  
        About purging data periodically
    4. Moving OpsCenter server to a different computer
      1.  
        About saving the files before moving the OpsCenter Server
      2.  
        Moving OpsCenter server because of constraints in upgrade
      3.  
        Moving OpsCenter server because of issues in the existing setup
  4. OpsCenter best practices
    1.  
      Network configuration best practices
    2. Installation and upgrade best practices
      1.  
        Things to avoid during installation and upgrade
    3. OpsCenter database best practices
      1.  
        Things to avoid while you use OpsCenter database
    4. Backup products best practices
      1.  
        Things to avoid while you collect data from backup products
    5.  
      OpsCenter Server best practices
    6.  
      OpsCenter reporting best practices
    7.  
      Best practices for antivirus configuration on Windows

Moving OpsCenter server because of issues in the existing setup

This section provides the procedure to move OpsCenter server to a different machine. You need to move OpsCenter server to a different machine in certain scenarios for example:

  • Faulty hardware

  • Hardware upgrade

  • Operating System upgrade

  • Moving from physical machine to virtual machine (or from virtual machine to physical machine)

To move OpsCenter server to a different machine

  1. Steps to be carried out on the OpsCenter source host

    On the OpsCenter source host, perform a backup of the OpsCenter database using the dbbackup script. You should run this script when you need to back up your OpsCenter database and database password file (db.conf).

  2. OpsCenter source host may have authentication (AT) data that you want to import into OpsCenter target host. You need to first export the AT data on the OpsCenter source host, which you can import into OpsCenter target host.

    Export the AT data to an xml file using the atutil utility. AT data comprises OpsCenterUsers(vx) users and certificates.

  3. Copy the XML file to the OpsCenter target host.

    Note:

    While copying the exported xml file, the DOS to UNIX conversion may result into garbage characters in the xml file that can cause import failure. To avoid this problem, copy the xml file through FTP and with binary format.

  4. Steps to be carried out on the OpsCenter target host

    Install OpsCenter on the new host that is target host.

  5. Stop all OpsCenter services.
  6. Carry out the performance tuning steps that you had done earlier.

    The new OpsCenter Performance and Tuning Guide provides information on how to tune OpsCenter for improved performance. The online version of the OpsCenter Performance and Tuning Guide can be found at:

    http://www.veritas.com/docs/DOC5808

  7. Restore the database that you have backed up earlier.

  8. Update the following information from the db.conf file:
    • If you are using the port that is different than the default one, update the value of the db.port as follows:

      db.port=13786

    • Set the db.serviceName parameter to the name of the target host as follows:

      db.serviceName=TargetHostName

  9. Import old authentication or AT data into OpsCenter target host.

    Make sure that you have copied the export xml file that you have created on the OpsCenter source host to OpsCenter target host.

    Run the following command for import:

    Windows

    <OpsCenterInstallLocation>\OpsCenter\server\authbroker\bin\atutil import -p <password of exported xml file> -f <location of xml file that contains old AT data> -z <location of AT data folder> - overwrite

    UNIX

    <OpsCenterInstallLocation>/SYMCOpsCenterServer/authbroker/bin/atutil import -p <password of exported xml file> -f <location of xml file that contains old AT data> -z <location of AT data folder> - overwrite

    Note:

    If the import is not successful, the default OpsCenter user needs to reset the passwords of OpsCenterUsers(vx) domain users that you have imported from the earlier OpsCenter version. Trust between NBAC-enabled NetBackup / PureDisk server and OpsCenter server need to be established again.

  10. Start OpsCenter services.