DPA9.1.85升級到DPA10.0.352流程

2024-06-28 14:32:54

字體：大中小

來源：轉載

供稿：網友

SolarWinds DPA的升級其實是一件非常簡單的事情，這里介紹一下從DPA 9.1.95升級到 DPA 10.0.352版本的流程。為什么要升級呢？ DPA給用戶發的郵件已經寫的非常清楚了（如下所示），DPA 10.0這個版本已開始支持MySQL了，另外它解決了一些Bug，在性能上有所改進、提升。

Our records indicate that you might have Database Performance Analyzer (DPA) 9.0 installed and licensed. If you have upgraded all your DPA servers to a later version (v9.1, 9.2, or 10.0), please ignore this email.

While SolarWinds transitioned Confio customers to a new licensing model in August 2014, it delayed the enforcement of core licenses for Oracle, DB2 and Sybase until November 10, 2015. If you are using DPA 9.0 with core licenses for Oracle, DB2 or Sybase, you should upgrade all your DPA servers to the latest version available in the Customer Portal before November 10, 2015. This will ensure that DPA can be configured to monitor all the databases that are licensed.

What will happen if I don’t upgrade?

DPA will start technically enforcing licenses for Oracle, DB2 and Sybase on November 10, 2015. If you are under your license limit, DPA will continue to collect data from all licensed database instances. If you have exceeded your licensing limit, DPA will unlicense all registered databases and stop monitoring them, and you will have to select which databases you want to monitor up to your license limit.

How many licenses will I have once I upgrade to a later version?

If you purchased Oracle, DB2 or Sybase licenses before August 1, 2014 and have not purchased more licenses since that time, your licenses were core-based. Core-based licenses have been converted to instances at a 4:1 ratio, and the new license keys in your Customer Portal reflect this converted amount.
If you initially purchased or bought additional licenses after August 1, 2014, your licenses are instance-based. The new license keys in your Customer Portal will reflect the purchased amount.

What should I do?

We recommend that you upgrade to the latest version of DPA available in your Customer Portal and activate your license keys before November 10, 2015. This will correctly align PRoduct enforcement with the licenses you purchased.

Are there other benefits to upgrading?

Yes, DPA has made a lot of progress since 9.0 was released:

9.1 added support for Amazon RDS databases, excluding SQL Statements from trend graphs and event annotations
9.2 added integration with Orion
10.0 added MySQL support
Bug fixes, security updates, and speed improvements

If you have any questions or concerns, please contact customer service at your earliest convenience. We apologize for the inconvenience and look forward to helping you quickly through this final transition of DPA licensing.

升級步驟：

1：首先你必須通過賬號去官網下載安裝文件。它提供Windows和linux兩個版本。我下載了Linux版本安裝文件SolarWinds-DPA-v10.0.352-SR1--Linux-Unix.tar.gz

2:解壓SolarWinds-DPA-v10.0.352-SR1--Linux-Unix.tar.gz安裝包，然后查看 readme.txt，你會看到下面升級指導步驟。強烈建議升級前，先看看reade.txt的UPGRADE INSTRUCTIONS。

clip_image001

3：還是建議將指導文檔的步驟調整一下，首先停止DPA的服務，禁用任何關于SolarWinds DPA的cron jobs。

[root@lnxmonitor ~]# cd /home/solarwinds/dpa_9_1_85/[root@lnxmonitor dpa_9_1_85]# lsiwc  license.txt  shutdown.sh  SolarWindsEula.rtf  startup.sh[root@lnxmonitor dpa_9_1_85]# ./shutdown.sh ****************************************************************************  If this script fails you can manually stop the program by *  doing the following steps: **  1) Set the java_HOME environment variable to your Java installation.*  2) Add <JAVA_HOME>/bin to your PATH environment variable.*  3) Go to the <DPA Home>/tomcat/bin directory. *  4) Run ./shutdown.sh *****************************************************************************Catalog exists...Found java 1.6 or 1.7JAVA HOME IS SET TO /home/solarwinds/dpa_9_1_85/iwc/jre_linuxPATH IS SET TO /home/solarwinds/dpa_9_1_85/iwc/jre_linux/bin:/usr/java/jdk1.7.0_25/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/binIBM Jvm Is Set To NOSetting the -server option for JVMJAVA_OPTS is  -server -Xss256k -Xms256m -Xmx1024m -Djsse.enableCBCProtection=false -XX:MaxPermSize=192m -Dcom.sun.management.jmxremote -Djava.net.preferIPv4Stack=true -Dnet.sf.ehcache.skipUpdateCheck=trueUsing CATALINA_BASE:   /home/solarwinds/dpa_9_1_85/iwc/tomcatUsing CATALINA_HOME:   /home/solarwinds/dpa_9_1_85/iwc/tomcatUsing CATALINA_TMPDIR: /home/solarwinds/dpa_9_1_85/iwc/tomcat/tempUsing JRE_HOME:        /home/solarwinds/dpa_9_1_85/iwc/jre_linuxUsing CLASSPATH:       /home/solarwinds/dpa_9_1_85/iwc/tomcat/bin/bootstrap.jar:/home/solarwinds/dpa_9_1_85/iwc/tomcat/ignite_config****************************************************************************  DPA is shutting down. ****************************************************************************Exiting script after webserver stopped.[root@lnxmonitor dpa_9_1_85]# 

4：安裝新版本DPA應用程序。

./dpa_10_0_352_x64_installer.sh 安裝過程的一些截圖如下所示

clip_image002

clip_image003

5：Copy/Move一些文件或文件夾到新的安裝目錄。

[root@lnxmonitor ~]# [root@lnxmonitor ~]# cd /home/solarwinds/[root@lnxmonitor solarwinds]# lsdpa_10_0_352  dpa_10_0_352_x64_installer  dpa_9_1_85[root@lnxmonitor solarwinds]# cp -fr /home/solarwinds/dpa_9_1_85/iwc/tomcat/ignite_config/* /home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/idc/system.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/idc/repo.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/idc/server.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/properties/sqlformat.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/properties/connection.pool.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/properties/mail.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/analysis/analysis.properties'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/analysis/wait_parameters.xml'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/readme.txt'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/security/sqlauth.xml'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/oracle_config/name_config_readme.txt'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/registration/massreg_sql_server_template.csv'? ycp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/registration/massreg_oracle_template.csv'? y  [root@lnxmonitor solarwinds]# cp -rf /home/solarwinds/dpa_9_1_85/iwc/tomcat/logs/* /home/solarwinds/dpa_10_0_352/iwc/tomcat/logs/ [root@lnxmonitor solarwinds]# mv /home/solarwinds/dpa_9_1_85/iwc/tomcat/licensing/ /home/solarwinds/dpa_10_0_352/iwc/tomcat/

如果你使用了SSL或LDPAS，或是修改了DPA的默認端口號。那么就必須參考文檔復制下面一些配置文檔。由于這里的升級案例不涉及這些，在此略過（其實也很簡單），具體參考文檔。

If you are:   - using LDAPS, or    - using SSL, or   - have changed the default SolarWinds DPA ports,   then also complete the following tasks:      a. Copy the keystore to the new installation.      cp -fr <OLD_home>/iwc/tomcat/conf/.keystore  <NEW_home>/iwc/tomcat/conf/   b. If you changed default port values or if you are using SSL on 9.1.x or      bellow, open server.xml from both the old and the new installation      directories and then manually copy over the appropriate values. Make      sure that ports on the HTTP and HTTPS connector are not conflicting.      The files are located at:          - <OLD_home>/iwc/tomcat/conf/server.xml          - <NEW_home>/iwc/tomcat/conf/server.xml

6：刪除安裝文件

[root@lnxmonitor solarwinds]# rm SolarWinds-DPA-v10.0.352-SR1--Linux-Unix.tar.gz  rm: remove regular file `SolarWinds-DPA-v10.0.352-SR1--Linux-Unix.tar.gz'? y [root@lnxmonitor solarwinds]# rm -rf dpa_10_0_352_x64_installer/

7：啟動DPA的服務。

./startup.sh *************************************************************************   If this script fails you can manually start the program by   doing the following steps:    1) Set the JAVA_HOME environment variable to your Java installation.  2) Add <JAVA_HOME>/bin to your PATH environment variable.  3) Go to the <DPA Home>/tomcat/bin directory.   4) Run ./startup.sh   5) Bring up the link (http://machine Name:8123      or http://machine IP:8123) in your browser.  **************************************************************************atalog exists...ound java 1.6 or 1.7AVA HOME IS SET TO /home/solarwinds/dpa_10_0_352/iwc/jre_linuxATH IS SET TO /home/solarwinds/dpa_10_0_352/iwc/jre_linux/bin:/usr/java/jdk1.7.0_25/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/binhe server port is 8127he HTTP port is 8123he HTTPS port is 8124PA is not running.he port 8123 is openhe port 8124 is openhe port 8127 is opentarting DPATACK_SIZE OVERRIDE = IN_HEAP_MEMORY OVERRIDE = AX_HEAP_MEMORY OVERRIDE = DDITIONAL_JVM_OPTION = BM Jvm Is Set To NOetting the -server option for JVMAVA_OPTS is  -server -Xss264k -Xms256m -Xmx1024m -XX:MaxPermSize=192m -Dcom.sun.management.jmxremote -Djava.net.preferIPv4Stack=true -Dnet.sf.ehcache.skipUpdateCheck=true aiting on initialization...please be patient *************************************************************************   DPA has been launched, wait one minute then bring up   one of the following links in your browser:   http://<Machine Name>:8123 or http://<Machine IP>:8123  https://<Machine Name>:8124 or https://<Machine IP>:8124   If the link does not work, check <iwc_dir>/tomcat/logs  and make sure a firewall is not running on this machine. **************************************************************************xiting script after webserver launched.