Plan the Upgrade or Migration

The path that you take for your upgrade or migration depends on various factors. Use the following sections to plan your upgrade:
capm370
The path that you take for your upgrade or migration depends on various factors. Use the following sections to plan your upgrade:
For cloud environments, see Rehydrating Data in a Cloud Environment.
Verify ETL Health
Before you upgrade, run the
etlHealth.sh
script. For releases 3.7.16 and higher, the script is included with the Data Repository installation. For earlier releases, contact Support. We recommend you run this script well in advance of the upgrade and again directly before the upgrade.
Follow these steps:
  1. Log in to one of the Data Repository nodes as the root user.
  2. Run the validation script:
    ./etlHealth.sh
    dauser
    dapassword
  3. Do one of the following:
    • If the health check passes, proceed with the upgrade.
    • If the health check fails, follow the instructions in the prompt to collect the irep and the data collected by the
      etlHealth.sh
      script, and submit these details in a Support ticket.
Plan the
CA Performance Management
Upgrade
Because releases 3.7 and higher upgrade the Data Repository to Vertica release 9.1, we support Data Repository upgrades directly from the following release only to 3.7:
  • CA Performance Management
    3.6
For
CA Performance Management
releases before 3.6, you must upgrade to the 3.6 release before upgrading the Data Repository to 3.7.
For other
CA Performance Management
components, we support upgrades directly from the following releases to 3.7:
  • CA Performance Management
    3.1
  • CA Performance Management
    3.2
  • CA Performance Management
    3.5
  • CA Performance Management
    3.6
The following table describes the best upgrade paths for indirect upgrades to 3.7:
Current Version
Upgrade Path
Older than 2.3.3
2.3.3 to 2.6 to 3.1 to 3.5 to 3.6 to 3.7 (Data Repository)
2.3.3 to 2.6 to 3.1 to 3.7 (other components)
2.3.3 through 2.4
2.6 to 3.1 to 3.5 to 3.6 to 3.7 (Data Repository)
2.6 to 3.1 to 3.7 (other components)
2.4.1
2.8 to 3.1 to 3.5 to 3.6 to 3.7 (Data Repository)
2.8 to 3.5 to 3.7 (other components)
2.5
3.0 to 3.5 to 3.6 to 3.7 (Data Repository)
3.0 to 3.6 to 3.7 (other components)
2.6
3.1 to 3.5 to 3.6 to 3.7 (Data Repository)
3.1. to 3.7 (other components)
2.7
3.1 to 3.5 to 3.6 to 3.7 (Data Repository)
3.2 to 3.7 (other components)
2.8
3.1 to 3.5 to 3.6 to 3.7 (Data Repository)
3.5 to 3.7 (other components)
3.0
3.5 to 3.6 to 3.7 (Data Repository)
3.6 to 3.7 (other components)
3.1
3.5 to 3.6 to 3.7 (Data Repository)
3.7 (other components)
3.2 through 3.5
3.6 to 3.7 (Data Repository)
3.7 (other components)
Plan the Operating System Upgrade or Install
The following operating systems were verified:
  • SUSE Linux Enterprise Server (SLES) 12 SP2
  • Oracle Linux (OL) 7.3 (Red Hat compatible kernel only)
The following Red Hat Enterprise Linux (RHEL) versions were verified:
A RHEL installation offers packages and add-ons.
CA Performance Management
supports a Minimal Install environment for RHEL.
  • RHEL 6.6 - 6.9
  • RHEL 7.4
  • RHEL 7.5
RHEL 6.8, 6.9, 7.3, or 7.4 are recommended.
To plan your OS upgrade and understand your upgrade scenario, review the following details and answer the following questions:
The following numbered questions correlate to the numbered decision steps in the following flowchart.
  1. If you have not yet, review the Upgrade Requirements and Considerations.
  2. Are you going to perform an OS installation (for example, going from RHEL 6.9 to RHEL 7.5 or SLES 12 SP2)?
    1. Is your current OS RHEL 5.x?
    2. Are you going to move to new hosts?
    3. Is RHEL 7.x, SLES, or OL the desired OS?
  3. Are you going to perform a minor OS upgrade (for example, RHEL 6.5 to RHEL 6.9)?
The following OS upgrade and install scenarios upgrade or install the OS for all components. However, your unique scenario might upgrade or install the OS for a select set of components.
Upgrade Scenarios
Review the following graphic to help identify your upgrade scenario. Then use the procedures that are outlined in the following sections. The following graphic provides a high-level overview of some common upgrade scenarios:
Plan_Upgrade
Plan_Upgrade
Upgrade
CA Performance Management
without an OS Upgrade
If this version of
CA Performance Management
supports your current OS, you can upgrade each component using its supported upgrade path. For more information, see Upgrading.
Upgrade
CA Performance Management
with a Minor OS Upgrade
If you are performing a minor OS upgrade (for example, RHEL 6.5 to RHEL 6.9), do the following tasks:
  1. Upgrade your OS.
  2. Upgrade each component using its supported upgrade path. For more information, see Upgrading.
Migrate to New Hosts from a Supported OS
Migration involves moving the
CA Performance Management
components, including configurations, customizations, and data, from one system to another system.
The following situations require migration:
  • You are moving to new hosts for an OS install (for example, RHEL 6.9 to RHEL 7.5 or SLES 12 SP2).
  • The current database hardware no longer meets sizing requirements.
  • You are moving from virtual machines to physical hardware for the database.
If you are moving
CA Performance Management
components to new systems with new IP addresses and hostnames from a supported OS, use the following procedures:
  1. Upgrade each component using its supported upgrade path. For more information, see Upgrading.
    You must upgrade the existing system to the product version you are migrating to before migrating.
  2. Depending on the amount of data, migrating the Data Repository can take a significant amount of time.
    To minimize downtime, perform incremental backups after your initial backup.
  3. This migration procedure copies over
    CA Performance Center
    and does not require you to install
    CA Performance Center
    on the new host.
  4. Update the Data Collector.
    1. For
      CA Mediation Manager
      , see the CAMM documentation.
    2. For
      CA Virtual Network Assurance
      , see the CA VNA documentation.
Migrate to New Hosts from an Unsupported OS
If your current OS is RHEL 5.x, you must first move to RHEL 6.x.
If you are moving
CA Performance Management
components to new systems with new IP addresses and hostnames from an unsupported OS, use the following procedures:
  1. Upgrade each component using its supported upgrade path until you reach a version from which you can upgrade directly to 3.7. For more information, see the Upgrading documentation for the version from which you are upgrading.
  2. Back up each component to another server:
    1. Depending on the amount of data, backing up and restoring the Data Repository can take a significant amount of time.
      To minimize downtime, perform incremental backups after your initial backup.
  3. Install the OS on each host.
  4. Install the same product version from your recent upgrade on each host. For more information, see the Installing documentation for the recommended version.
  5. Restore each component:
    For each component, verify that the backup is copied over.
  6. Upgrade each component to this product version. For more information, see Upgrading.
  7. Depending on the amount of data, migrating the Data Repository can take a significant amount of time.
    To minimize downtime, perform incremental backups after your initial backup.
  8. This migration procedure copies over
    CA Performance Center
    and does not require you to install
    CA Performance Center
    on the new host.
  9. Update the Data Collector.
    1. For
      CA Mediation Manager
      , see the CAMM documentation.
    2. For
      CA Virtual Network Assurance
      , see the CA VNA documentation.
Perform an OS Installation from a Supported OS
If you are performing a major OS upgrade from a supported OS (for example, RHEL 6.9 to RHEL 7.5 or SLES 12 SP2) on the same systems with the same IP addresses and hostnames, use the following procedures:
  1. Upgrade each component using its supported upgrade path. For more information, see Upgrading.
    You must upgrade the existing system to the product version you are backing up and restoring to before backing up and restoring.
  2. Back up each component to another server:
    1. Depending on the amount of data, backing up and restoring the Data Repository can take a significant amount of time.
      To minimize downtime, perform incremental backups after your initial backup.
  3. Update the Data Collector.
    1. For
      CA Mediation Manager
      , see the CAMM documentation.
    2. For
      CA Virtual Network Assurance
      , see the CA VNA documentation.
  4. Install the OS on each host.
  5. Install this product version on each host. For more information, see Installing.
  6. Restore each component:
    For each component, verify that the backup is copied over.
Perform an OS Installation from an Unsupported OS
If your current OS is RHEL 5.x, you must first move to RHEL 6.x.
If you are performing a major OS upgrade from an unsupported OS (for example, RHEL 5.x to RHEL 6.9) on the same systems with the same IP addresses and hostnames, use the following procedures:
  1. Upgrade each component using its supported upgrade path until you reach a version from which you can upgrade directly to 3.7. For more information, see the Upgrading documentation for the version from which you are upgrading.
  2. Back up each component to another server:
    1. Depending on the amount of data, backing up and restoring the Data Repository can take a significant amount of time.
      To minimize downtime, perform incremental backups after your initial backup.
  3. Update the Data Collector.
    1. For
      CA Mediation Manager
      , see the CAMM documentation.
    2. For
      CA Virtual Network Assurance
      , see the CA VNA documentation.
  4. Install the OS on each host.
  5. Install the same product version from your recent upgrade on each host. For more information, see the Installing documentation for the recommended version.
  6. Restore each component:
    For each component, verify that the backup is copied over.
  7. Upgrade each component to this product version. For more information, see Upgrading.