Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Below are instructions on the steps needed to upgrade a Zephyr Enterprise Data Center installation of 4.7 to the latest 5.0.

Prerequisites for Zephyr 5.0 installation:

  1. Database ready with remote access permission
  2. All the nodes should be in same time zone
  3. Zephyr build should be same all the nodes
  4. Upgrader

Steps

  1. Take a full back up of the existing Zephyr Enterprise Data Center instance using the information at Backup & Restore.
  2. Run the 5.0 Upgrader Utility in check mode to verify the backup is ready to be upgraded. If any errors appear during this process, please reach out to Zephyr Support before proceeding.
  3. On every node (even if just one), uninstall Zephyr Enterprise Data Center 4.7
    1. IMPORTANT: All configurations and settings will be lost during uninstallation. Create a backup of these settings before uninstalling in case they are needed for review in later steps.
  4. On every node (even if just one), install Zephyr Enterprise Data Center 5.0 (14587)
    1. See our installation guide if you need help here
  5. Drop all database tables in the MySQL database for ITCC and DVERSION if they exist
  6. Stop all Zephyr Enterprise Data Center application nodes before running the upgrade process on the database
  7. Run the 5.0 Upgrader Utility in Upgrade mode. Use the same backup you checked in step 2 above.
    1. Use the formatd below to run the utility and point the utility to where your MySQL server and my.ini/my.cnf file are located
      1. Windows

        <Upgrader>.exe -VzMySQLPath='C:\Program Files\MySQL\MySQL Server 5.6\bin\mysql.exe' -VzMySQLCnfFilePath='C:\Program Files\MySQL\MySQL Server 5.6\<your_ini_file>'
      2. Linux

        <Upgrader>.sh -VzMySQLPath='/usr/bin/mysql' -VzMySQLCnfFilePath='/etc/mysql/<your_cnf_file>'
  8. Once upgrade is complete, start all application nodes and verify the upgrade completion by logging into the instance and checking data
  • No labels