Page tree

Skip to end of metadata
Go to start of metadata

This topic presents instructions to prepare the App Visibility Manager environment for an upgrade, and describes compatibility consideration for the upgrade.

Backing up the App Visibility database

Make a physical backup of the App Visibility PostgreSQL database to protect your data from loss. The output of a physical backup contains the data files that the App Visibility server can use directly, resulting in a faster recovery operation.

To create an App Visibility database backup file

  1. On the computer with the App Visibility portal or collector, navigate to the following directory:
    • (Windows)
      collector_installationDirectory\collector\bin\db
      or portal_installationDirectory\portal\bin\db
    • (Linux)
      collector_installationDirectory/collector/bin/db
      or portal_installationDirectory/portal/bin/db
    If the portal and collector are installed on the same computer, they share a database, and you only need to perform the procedure in one place.
    If the portal and collector are on separate computers, perform the backup procedure on both components at the same time so that the backup content is consistent. Otherwise, the backup content does not match and the data is incorrect when restored.
  2. Run the following script:
    • (Windows) create-pgsql-dump.bat
    • (Linux) ./create-pgsql-dump.sh

The script creates a backup of the data in the avdb.dump file in the server component's installationDirectory\ADOP_DB\pgsql\backup directory.

For more information about making PostgreSQL database backup files, see Backup and Restore .

Recovering the App Visibility database data

If you have issues with your database, you can recover the backed-up data file.

To recover the backed up App Visibility data file

  1. Ensure that the avdb.dump file is in the server component's installationDirectory\ADOP_DB\pgsql\backup directory.
  2. Stop the component service:
    • On the computer with the App Visibility portal, stop the portal service.
    • On the computer with the App Visibility collector, stop the collector service.
    For information about stopping services, see Starting and stopping the App Visibility server services.
  3. Navigate to the following directory, according to your system:
    • (Windows)
      collector_installationDirectory\collector\bin\db
      or portal_installationDirectory\portal\bin\db
    • (Linux)
      collector_installationDirectory/collector/bin/db
      or portal_installationDirectory/portal/bin/db
    If the portal and collector are installed on the same computer, they share a database, and you only need to perform the procedure in one place.
    If the portal and collector are on separate computers, perform the recovery procedure on both components at the same time so that the content is consistent. Otherwise, the content does not match and the data is incorrect when restored.
  4. Run the following script:

    • (Windows) restore-pgsql-dump.bat
    • (Linux) ./restore-pgsql-dump.sh
  5. Start the component service.

The database data is recovered.

For more information about how to recover the PostgreSQL database data, see Backup and Restore .

Backing up customized App Visibility agent policies

If you created a customized agent policy, including adding comments, copy the contents of the policy and save it as a text file. This backup file can be used to compare the previous settings with the current.

  1. In the navigation pane of the TrueSight console, select Administration > App Visibility Agent Policies.
  2. Click the name of the agent policy you want to back up.
  3. Copy the contents of the agent policy and paste them into a text file.
  4. Save the text file as a back up.

If you customized other settings with the help of BMC Support, contact them for assistance backing up the settings.

Recovering customized App Visibility agent policies

  1. In the navigation pane of the TrueSight console, select Administration > App Visibility Agent Policies.
  2. Click the name of the agent policy you want to back up.
  3. Copy the contents from the saved text file and paste them into the agent policy.

  4. Save the agent policy.

Backing up synthetic SLA data

Before you upgrade the App Visibility server, use the Synthetic Transaction SLA Report utility to back up your synthetic SLA data to mitigate problems that might occur during migration of the data. 

See Generating report data with the BMC Synthetic Transaction SLA Report utility for more details about running the Synthetic Transaction SLA Report utility.

Checking upgrade compatibility

Consider the following version compatibility behaviors with the App Visibility upgrade:

Component versions

  • Integration with TrueSight Operations Management components: Install or upgrade Infrastructure Management components , including the latest patches.
    You will not be able to see the latest updates in the TrueSight console, though, until you upgrade the Presentation Server. For details about the order to upgrade components, see Upgrading App Visibility Manager components.

  • App Visibility version of server and agents. You must upgrade all the server components (portal, all collectors, and all proxies) and agents, including TEA Agents.
    • App Visibility server version. You can upgrade the App Visibility server components from version 10.1 to the current version of App Visibility. For earlier versions of the App Visibility server, upgrade to server version 10.1 and then upgrade to the current version.

      Warning

      When you upgrade the App Visibility server, you can enable high-availability configuration for the App Visibility portal and collectors. After you enable HA for the portal, you must delete and then add an App Visibility portal to the Presentation Server. Enter the FQDN and the port of the portal's load balancing server.

      All App Visibility dashlet configuration is lost in this process and you will need to reconfigure the dashlets:

      • Application Client Breakdown dashlet
      • Application Server Health dashlet
      • Application View dashlet
      • Applications dashlet
      • Availability and Performance dashlet
      • Impacted Users or Executions dashlet
      • Top Real Transactions dashlet

      Do not delete the App Visibility portal from the Presentation Server before upgrading. Deleting the portal before upgrading will cause a loss of historic synthetic monitoring data.

    • Agent version. Upgrade the App Visibility agents from version 10.0, or later, to the current version of App Visibility. You must upgrade all agents, including TEA Agents, to the current version.

      For earlier versions of the agents, do the following procedures:

      Upgrade componentSteps
      App Visibility agent for Java
      1. Upgrade to version 10.0 from an earlier version.
      2. Upgrade to the current version from version 10.0, or later.
      App Visibility agent for .NET
      1. Upgrade to version 10.0 from an earlier version.
      2. Upgrade to the current version from version 10.0, or later.
      Synthetic TEA AgentUpgrade to the current version.

Policy and configuration files

  • Out-of-the-box policy and configuration files. When you upgrade the server, all out-of-the-box policy files and configuration files are automatically upgraded , and the policies can work with the supported agents.
  • Customized policy and configuration files. When you upgrade the server, all customized policy files are merged with the upgraded files. Existing functionality and values are retained for earlier agents, and new functionality is added for upgraded agents.

    If you added comments to customized files, the comments are not retained after upgrade.

Where to go from here

Upgrade the App Visibility server and verify the upgraded version.