Upgrade Guide Version 7.2

Transcription

1 Upgrade Guide Version 7.2 Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

2 DISCLAIMER IBM believes that the information in this publication is accurate as of its publication date. The information is subject to change without notice. COPYRIGHT Copyright IBM Corporation All Rights Reserved. Printed October Use, copy, and distribution of any IBM software described in this publication needs an applicable software license. No part of this product or document may be reproduced, stored in a retrieval system, or transmitted, in any form by any means, electronic, mechanical, photocopy, recording, or otherwise, without prior written authorization of IBM Corporation and its licensers, if any. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

3 Upgrading to Resiliency Orchestration Server 7.2 This section describes how to upgrade Sanovi Cloud Continuity 7.1 SP1/SP2/SP4/SP6 to Resiliency Orchestration Server 7.2. Overview Resiliency Orchestration 7.2 release requires RHEL 7.3 operating system and uses mariadb as the database. Prior versions of the software were supported on RHEL 6.x or lower and were using Mysql as the database. Before upgrading your existing Sanovi Cloud Continuity software to the new version, you would need to upgrade the server operating system (OS) to RHEL 7.3 and install required mariadb database. However, while you prepare your server for the required OS and the database, you need to retain your existing Sanovi Cloud Continuity software and the data by backing them up on another machine and restoring from there. Alternatively, you can prepare a new server machine with the required OS and database softeware and copy over the existing Sanovi Cloud Contuinity software and your existing data to the new server hardware before you proceed with upgrade to Resiliency Orchestration 7.2. Prerequisites Whether you upgrade the existing server with the required OS and database or use a new server hardware, you must use the same IP. Upgrade should be performed only when all the groups are in "Normal Inactive" or "Normal Reset" state. No operations/workflows should be executing. If NormalCopy/FailOver/ SwitchOver/SwitchBack or any Business Process/Test/Policy is in progress, it should be completed, stopped, or aborted so that the group can be moved to Normal Inactive state. Use "Change continuity" option to move the group to "Normal Inactive" or Normal Reset". Preparing For Upgrade 1. Stop Sanovi DRM Server Services by using the following command: $EAMSROOT/bin/panaces stop 2. Stop all remote agents before upgrade by using the following command: $EAMSROOT/bin/DRMAgentsStop.sh ALL 3. Perform backup of Sanovi Cloud Continuity software and configuration files using the given Backup Plan. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

4 Backup Plan Take backup of the following files and directories on a backup server within the network o Sanovi Server Mysql Metadata mysqldump -u root --databases panaces pfr advancedreporter -R --triggers > backupfilename.sql o Sanovi Server Installation directory $EAMSROOT o The following system files: i) sysctl.conf ii) any user specific scripts and cron jobentries iii) /etc/hosts o User files, if any o If Panaces Server is configured with Linux OS agent: Agent Binaries Custom/Field Specific scripts 4. Upgrade the Sanovi Cloud Contuinity server operating system to RHEL Install mariadb and configure as per Resiliency Orchestration 7.2 Installation Guide 6. Install Tomcat and configure as per Resiliency Orchestration 7.2 Installation Guide 7. Stop all the services in the current Cloud Continuity Server. 8. Take the mysql Schema a. mysqldump -u root databases panaces pfr advancedreporter triggers -R > /backup/panaces-pfr-advrpt.sql 9. Take EAMSROOT, and TOMCAT Home folder backup a. cd /opt b. tar cvzf /backup/eamsroot.tar.gz panaces c. cd /opt/ d. tar cvzf /backup/tomcat7.tar.gz jboss-ews Note down the port exceptions in firewall, use system-config-firewall or systemconfig-securitylevel 11. Copy /backup/panaces-pfr-advrpt.sql /backup/eamsroot.tar.gz /backup/tomcat7.tar.gz /etc/security/limit.conf /etc/hosts /etc/my.cnf to /backup of new IBM Resiliency Orchestration server using scp. 12. Login to new IBM Resiliency Orchestration server using putty 13. Extract IBM Resiliency Orchestration binaries a. cd /opt b. tar xvzf /backup/ EAMSROOT.tar.gz 14. Extract Tomcat a. cd /opt b. tar xvzf /backup/tomcat7.tar.gz 15. Update EAMSROOT a. echo export EAMSROOT=/opt/panaces >> /etc/profile Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

5 16. refer /backup/limit.conf, /backup/hosts, /backup/my.cnf and update /etc/security/limit.conf /etc/hosts /etc/my.cnf respectively 17. configure the exception ports as noted earlier using system-config-firewall or systemconfig-securitylevel 18. Restore the mysql schema a. mysql -u root < /backup/panaces-pfr-advrpt.sql 19. Verify the panaces, pfr, advancedreporter databases are available after restored in the new server. 20. Create required database users along with privileges a. Mysql u root b. use mysql; c. CREATE USER 'pfradmin'@'localhost' IDENTIFIED BY 'pfradmin123'; d. GRANT ALL PRIVILEGES ON *.* TO 'pfradmin'@'localhost' IDENTIFIED BY 'pfradmin123' WITH GRANT OPTION; e. CREATE USER 'panaces'@'localhost' IDENTIFIED BY 'panaces123'; f. GRANT ALL PRIVILEGES ON *.* TO 'panaces'@'localhost' IDENTIFIED BY 'panaces123' WITH GRANT OPTION; g. CREATE USER 'sanovireporter'@'localhost' IDENTIFIED BY 'sanovi123'; h. GRANT ALL PRIVILEGES ON *.* TO 'sanovireporter'@'localhost' IDENTIFIED BY 'sanovi123' WITH GRANT OPTION; Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

6 Upgrading Resiliency Orchestration Server in GUI mode Perform the following steps for upgrading Sanovi Cloud Continuity server. The commands specified in the following points must be provided at the command prompt. 1. Download the server binaries 2. Sanovi Cloud Continuity Server can be upgraded to Resiliency Orchestration 7.2 by loging in as a sanovi user and executing the following command: (Use whichever is applicable) Note sh install.bin (or)./install.bin Make sure that you have free space of approximately 800 MB in /tmp directory, before executing the above command. 3. Resiliency Orchestration Server upgrade starts with the following screen:. Figure 1: Resiliency Orchestration Installer 4. After displaying the Resiliency Orchestration Installer screen, the MySQL root password window is displayed. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

7 Figure 2: Resiliency Orchestration Server Upgrade - MySQL root password 5. Enter MySQL root user password and click Next. The Tomcat Home window is displayed. Figure 3: Resiliency Orchestration Server Upgrade - Tomcat Home 6. Click Choose to browse and select the location of Tomcat. When Tomcat is located and then selected, the path appears in the Please Choose a Folder: box in Tomcat Home screen. Click Next, the Introduction window is displayed. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

8 Figure 4: Resiliency Orchestration Server Upgrade - Introduction 7. Click Next. The License Agreement window is displayed Figure 5: Resiliency Orchestration Server Upgrade - License Agreement 8. Click the appropriate option button after perusal of the License Agreement. The options are: 1. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

9 Option Button I accept the terms of the License Agreement I do NOT accept the terms of the License Agreement Description Click this option button for acceptance of the License Agreement. Click this option button for rejection of the License Agreement. By default, this is selected. The Next button is unavailable with this option. 9. Click Next (on acceptance of the License Agreement window) to proceed with the installation. The Choose Install Folder window is displayed. Figure 6: Resiliency Orchestration Server Upgrade - Choose Install Folder 10. Select a path to install the software by clicking Choose. Choose the path where the Panaces is currently installed. Note The 7.1 will be installed in the same path by renaming the existing installation folder by appending the release name. For example, if 7.1 is installed in /opt/panaces then the folder will be renamed to /opt/panaces_7.1_sp6 containing the old installation, while /opt/panaces will be installed with Click Next to continue. 12. The Choose Install Set window is displayed. The Choose Install Set screen will be displayed only when the user selects the install location same as the current one. Select Upgrade icon. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

10 Figure 7: Resiliency Orchestration Server Upgrade - Choose Install Set Note If Typical is selected and Resiliency Orchestration Server version 7.2 is present in the system, then the following error is displayed. Click Quit Installation to cancel the upgrade process. The Resiliency Orchestration Server version is already installed in this machine. Installer cannot overwrite the existing installation.. The installer will quit now. 13. Click Next. The Pre-Installation Summary window is displayed. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

11 Figure 8: Resiliency Orchestration Server Upgrade - Pre-Installation Summary 14. Go through the pre-installation summary to verify the inputs provided. If you want to change the inputs, click Previous and modify. 15. Click Install. The Installing Resiliency Orchestration Server window is displayed. Note By now, the older installation folder has been renamed by appending the release name. So if the installation is cancelled then the older installation folder has to be renamed to original folder by the user as part of the fallback plan. For example, if 7.1 is installed in /opt/panaces then the folder will be renamed to /opt/panaces_7.1_sp6. If the upgrade is canceled any further, user has to rename /opt/panaces_7.1_sp6 to /opt/panaces to restart upgrade or to use the older version of the product. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

12 2. Figure 9: Resiliency Orchestration Server Upgrade - Installing Resiliency Orchestration Server 16. Once the installation is complete, the Upgrade Complete window is displayed indicating successful upgrade. 17. Click Done to complete the upgrade process. Post Installation Steps 1. Download ThirdPartyJSLib.zip from the link GPL dependent binaries ( Copy ThirdPartyJSLib.zip to $TOMCAT_HOME/webapps/PanacesGUI/scripts/. Unzip ThirdPartyJSLib.zip in the $TOMCAT_HOME/webapps/PanacesGUI/scripts/. Remove ThirdPartyJSLib.zip from $TOMCAT_HOME/webapps/PanacesGUI/scripts/. 2. If you would like to use the vault integration feature of the product, complete the instructions given below: a. Ensure that the required vault integration library files from your vault vendor are available with you. b. Add all the vault integration library files to the following locations. {TOMCAT_HOME}/webapps/PanacesGUI/WEB-INF/lib {TOMCAT_HOME}//webapps/PanacesGUI/pages/classes/lib {TOMCAT_HOME}//webapps/userPortal/WEB-INF/lib {TOMCAT_HOME}//webapps/userPortal/pages/classes/lib {EAMSROOT}/agents/vault/{yourVaultName}/lib Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

13 {EAMSROOT}/lib Note You need to set the execute (770) and Tomcat user group permissions for the vault integration library files in the TOMCAT_HOME locations. You need to set the execute (770) and Panaces user group permissions for the vault integration library files in the EAMSROOT locations. 3. Server is by default enabled with TLS 1.2 security. In order to achieve backwards compatibility to support older agents, open $EAMSROOT/installconfig/panaces.properties and set If Agents are from 7.1 Release panaces.acp.communicationtype = SECURE If Agents are from 6.3 Release panaces.acp.communicationtype = NONSECURE 4. Resiliency Orchestration Services ; /opt/panaces/bin/panaces start 5. Verify that the console log shows panaces services started successfully tail f /opt/panaces/var/log/console.log 6. Once server has started, go to $EAMSROOT/lib/ and run the following sql script mysql -uroot < mysql_schema_upgrade_after_server_startup_jr_to_jy.sql Fallback Plan At any time of the upgrade, if there are failures that cannot be corrected within the upgrade window, use the following plan to restore to the old Sanovi server installation. 1. Drop the existing databases if they already exist a. mysqladmin u root drop panaces b. mysqladmin u root drop pfr c. mysqladmin u root drop advancedreporter 2. Restore the MySQL Metadata from backup. mysql -u root < backupfilename.sql 3. Restore the Sanovi Server software installation directory (7.1). 4. Startup Sanovi Server Services. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

14 Upgrading to Resiliency Orchestration Server 7.2 SP1 This section describes how to upgrade Resiliency Orchestration 7.2 to Resiliency Orchestration Server 7.2 SP1. Prerequisites For upgrading, the existing setup should be IBM Resiliency Orchestration 7.2 with the 7.2 P1 patch applied. Upgrade should be performed only when all the groups are in "Normal Inactive" or "Normal Reset" state. No operations/workflows should be executing. If NormalCopy/FailOver/ SwitchOver/SwitchBack or any Business Process/Test/Policy is in progress, it should be completed, stopped, or aborted so that the group can be moved to Normal Inactive state. Use "Change continuity" option to move the group to "Normal Inactive" or Normal Reset". Preparing For Upgrade 1. Stop IBM Resiliency Orchestration Server Services by using the following command: $EAMSROOT/bin/panaces stop 2. Stop all remote agents before upgrade by using the following command: $EAMSROOT/bin/DRMAgentsStop.sh ALL 3. Perform backup of IBM Resiliency Orchestration Server software and configuration files using the given Backup Plan. Backup Plan Take backup of the following files and directories on a backup server within the network o IBM Resiliency Orchestration Server Mysql Metadata mysqldump -u root --databases panaces pfr advancedreporter -R -- triggers > backupfilename.sql o The following system files: i) sysctl.conf ii) any user specific scripts and cron jobentries iii) /etc/hosts o User files, if any o If Panaces Server is configured with Linux OS agent: Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

15 Agent Binaries Custom/Field Specific scripts 4. Stop all the services in the current IBM Resiliency Orchestration Server. 5. Take TOMCAT Home folder backup a. cd /opt/ b. tar cvzf /backup/tomcat7.tar.gz jboss-ews Note down the port exceptions in firewall, use system-config-firewall or systemconfig-securitylevel Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

16 Upgrading Resiliency Orchestration Server in GUI mode Perform the following steps for upgrading IBM Resiliency Orchestration server. The commands specified in the following points must be provided at the command prompt. 1. Download the server binaries 2. IBM Resiliency Orchestration Server can be upgraded to Resiliency Orchestration 7.2 SP1 by loging in as a sanovi user and executing the following command: (Use whichever is applicable) Note sh install.bin (or)./install.bin Make sure that you have free space of approximately 800 MB in /tmp directory, before executing the above command. 3. Resiliency Orchestration Server upgrade starts with the following screen:. Figure 10: Resiliency Orchestration Installer 4. After displaying the Resiliency Orchestration Installer screen, the MySQL root password window is displayed. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

17 Figure 11: Resiliency Orchestration Server Upgrade - MySQL root password 5. Enter MySQL root user password and click Next. The Tomcat Home window is displayed. Figure 12: Resiliency Orchestration Server Upgrade - Tomcat Home 6. Click Choose to browse and select the location of Tomcat. When Tomcat is located and then selected, the path appears in the Please Choose a Folder: box in Tomcat Home screen. Click Next, the Introduction window is displayed. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

18 Figure 13: Resiliency Orchestration Server Upgrade - Introduction 7. Click Next. The License Agreement window is displayed Figure 14: Resiliency Orchestration Server Upgrade - License Agreement 8. Click the appropriate option button after perusal of the License Agreement. The options are: Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

19 Option Button I accept the terms of the License Agreement I do NOT accept the terms of the License Agreement Description Click this option button for acceptance of the License Agreement. Click this option button for rejection of the License Agreement. 9. Click Next (on acceptance of the License Agreement window) to proceed with the installation. The Choose Install Folder window is displayed. Figure 15: Resiliency Orchestration Server Upgrade - Choose Install Folder 10. Select a path to install the software by clicking Choose. Choose the path where the Panaces is currently installed. Note The 7.2 SP1 will be installed in the same path by renaming the existing installation folder by appending the release name. For example, if 7.2 is installed in /opt/panaces then the folder will be renamed to /opt/panaces_7.2 containing the old installation, while /opt/panaces will be installed with 7.2 SP Click Next to continue. 12. The Choose Install Set window is displayed. The Choose Install Set screen will be displayed only when the user selects the install location same as the current one. Select Upgrade icon. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

20 Figure 16: Resiliency Orchestration Server Upgrade - Choose Install Set Note If Typical is selected and Resiliency Orchestration Server version 7.2 SP1 is present in the system, then the following error is displayed. Click Quit Installation to cancel the upgrade process. The Resiliency Orchestration Server version is already installed in this machine. Installer cannot overwrite the existing installation.. The installer will quit now. 13. Click Next. The Pre-Installation Summary window is displayed. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

21 Figure 17: Resiliency Orchestration Server Upgrade - Pre-Installation Summary 14. Go through the pre-installation summary to verify the inputs provided. If you want to change the inputs, click Previous and modify. 15. Click Install. The Installing Resiliency Orchestration Server window is displayed. Note By now, the older installation folder has been renamed by appending the release name. So if the installation is cancelled then the older installation folder has to be renamed to original folder by the user as part of the fallback plan. For example, if 7.2 is installed in /opt/panaces then the folder will be renamed to /opt/panaces_7.2. If the upgrade is canceled any further, user has to rename /opt/panaces_7.2 to /opt/panaces to restart upgrade or to use the older version of the product. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide

22 3. Figure 18: Resiliency Orchestration Server Upgrade - Installing Resiliency Orchestration Server 16. Once the installation is complete, the Upgrade Complete window is displayed indicating successful upgrade. 17. Click Done to complete the upgrade process. Post Installation Steps Fallback Plan At any time of the upgrade, if there are failures that cannot be corrected within the upgrade window, use the following plan to restore to the old IBM Resiliency Orchestration Server installation. 1. Drop the existing databases if they already exist a. mysqladmin u root drop panaces b. mysqladmin u root drop pfr c. mysqladmin u root drop advancedreporter 2. Restore the MySQL Metadata from backup. mysql -u root < backupfilename.sql 3. Restore the IBM Resiliency Orchestration Server software installation directory (7.2). 4. Startup IBM Resiliency Orchestration Server Services. Copyright IBM Corporation Resiliency Orchestration Upgrade Guide