Preparing for an App Visibility upgrade and checking compatibility

To upgrade App Visibility Manager components from version 10.0, prepare your system and review compatibility differences so that you can maximize the benefits of the upgrade without losing data or custom configurations.

The following topics prepare your App Visibility system for upgrade, and describe compatibility consideration:

• • (Version 10.0) Backing up and recovering data for a MySQL database
  • Backing up customized App Visibility agent policies
  • Recovering customized App Visibility agent policies
  • Backing up synthetic SLA data
  • Increasing parameter for required system changes
  • Checking upgrade compatibility
  • Expected downtime during upgrade
  • Where to go from here
  • Related topics

(Version 10.0) Backing up and recovering data for a MySQL database

If you are upgrading from version App Visibility version 10.0, BMC recommends that you, as the database administrator, make a physical backup of the database data files before performing the upgrade. The output of a physical backup contains data files that the MySQL database can use directly, in case you want to revert to the previous version.

To create a MySQL database backup file

1. On the computer with the App Visibility portal or collector, navigate to the following directory:

   • (Windows) serverInstallationDirectory\collector\bin\db or serverInstallationDirectory\ portal\bin\db
   • (Linux)  serverInstallationDirectory/collector/bin/db or serverInstallationDirectory/ 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.

2. Run the following script:
   • (Windows) create-mysql-dump.bat
   • (Linux) ./create-mysql-dump.sh

The script creates a backup of the data in the ad-mysql-dump.sql file.

For more information about making MySQL backup files, see Database Backup Methods.

To recover a backed up MySQL database

If you need to recover the backed up MySQL database, use the following procedure.

1. On the computer with the App Visibility portal or collector, log in to the MySQL database as a root user.
   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.
2. Run the following commands:
   drop database adops_collector
   drop database adops_portal
3. Navigate to the following directory:
   
   • (Windows)   serverInstallationDirectory\ADOP_DB\bin
   • (Linux)  serverInstallationDirectory/ADOP_DB/mysql-5.6.14/bin
4. Run the following script:
   • (Windows)  restore-mysql-dump.bat
   • (Linux)  ./restore-mysql-dump.sh
5. Restart the portal and collector services.

The database data is recovered.

For more information about how to recover the MySQL database data, see MySQL backup and recovery methods.

Ensure that you have enough disk space to make a full copy of the database. The upgrade utility makes a temporary copy of the database to enable rolling back to version 10.0 if the upgrade has problems.

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

Under some circumstances, synthetic SLA data is not migrated properly. The following error appears in the adops_server_install.log file.

To help mitigate the problem, we recommend that you back up your synthetic SLA data using the Synthetic Transaction SLA Report utility before upgrading App Visibility.

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

Increasing parameter for required system changes

Before you upgrade to version 10.1, increase the value of cp.remove.abandoned.timeout.sec property to 300 seconds (five minutes) in the collector.properties file.

If the database is over 50 GB, increase the value to 480 seconds (eight minutes).

The collector.properties file is located in the following directory:

1. 
   
   • Windows
     installationDirectory\collector\properties
   • Linux
     installationDirectory/collector/properties

Checking upgrade compatibility

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

Expected downtime during upgrade

For the App Visibility server components, the upgrade process stops the services and restarts them at the end of the process. While you upgrade the App Visibility portal and collector, the components are down during data migration. The BMC test environment took five hours to migrate a 200 GB database. Your results may vary.

Where to go from here

The following topics describe how to upgrade and verify your installed version of App Visibility components to the latest version:

• Upgrading-the-App-Visibility-server
• Upgrading-App-Visibility-agents-for-Java
• Upgrading-App-Visibility-agents-for-NET

• Upgrading-synthetic-TEA-Agents

Related topics

Downloading-the-installation-files

App-Visibility-system-requirements

Installing-App-Visibility-components

Backing-up-and-recovering-the-App-Visibility-database