Documentation forDatabase Performance Analyzer

Upgrade DPA on an Amazon Machine Image instance

If you are upgrading from DPA 2022.3 and you configured DPA 2022.3 for SAML authentication, be aware that DPA 2022.4 and later include changes to the SAML configuration. After the upgrade, no one will be able to log in with SAML until you update the configuration.

  • Before you upgrade, make sure you have a local login available.

  • After the upgrade, log in as a local user and complete the steps under "SAML configuration changes" in the DPA 2022.4 Release Notes to update the SAML configuration.

If you're using DPA in Amazon Web Services (AWS) with AWS Marketplace Metering Service, complete the following steps to upgrade to the latest version.

  1. Open a remote connection (SSH) and log in to your DPA instance in Amazon EC2.

  2. Download the most recent version of SolarWinds DPA. Use the link provided in the new version notification banner.

    If the server you are upgrading on has Internet access, you can download DPA directly to that server. If not, you can download DPA to a different computer and then use SCP to transfer it.

  3. Enter the following command to turn off the scheduled job that restarts DPA if it stops:

    cmd> crontab -r

  4. Install the new version in a new directory on your existing server.
  5. Run ./shutdown.sh from the old installation directory.

  6. Locate the directory that was created when you installed the new version:

    /home/dpa_x_x_xxx = old installation home

    /home/dpa_12_x_xxx = new DPA home

  7. Copy or move these directories from the old installation to the new:

    /iwc/tomcat/ignite_config/
    /iwc/tomcat/logs/

    Do not copy hotfix files.

    For example:

    mv OLD_home/iwc/tomcat/ignite_config/* NEW_home/iwc/tomcat/ignite_config/

    or

    cp -rp OLD_home/iwc/tomcat/ignite_config NEW_home/iwc/tomcat/ignite_config

  8. If you changed the default SolarWinds DPA ports, then you must modify the server.xml file in the new installation to incorporate the port changes from your earlier installation.
  9. Run ./startup.sh from the new directory.

  10. Turn the cron job back on:

    1. Open crontab in edit mode:

      cmd> crontab -e

    2. Add the following line:

      * * * * * <FULL_PATH_TO_STARTUP_SCRIPT> > <FULL_PATH_TO_STARTUP_LOG> 2>&1

      For example:

      * * * * * /home/ec2-user/dpa_12_0_3074/startup.sh > /home/ec2-user/dpa_12_0_3074/startup.log 2>&1

    3. Save your changes.

Resize to a larger Amazon AWS instance type

The t2.medium Amazon EC2 instance type is sufficient only for monitoring up to 20 database instances. Resize your AWS instance type as your monitoring needs grow.

For more information, search "Resizing Your Instance" at http://aws.amazon.com/documentation.