10.0 Upgrading/Migrating a Multiple-appliance TeamWorks Deployment

Moving your TeamWorks deployment to version 18.2 involves two interwoven processes:

  • Deploying replacement TeamWorks 18.2 appliances.

  • Migrating your TeamWorks system data (users, groups, conversations, attachments, etc.) to the newly deployed appliances.

Before You Upgrade!

Failure to comply with the following critical points could result in a non-functional TeamWorks system.

Critical Point

Details

  • Verify the appliance versions

  • Make sure that all appliances targeted for upgrading to version 18.2 are running version 18.1.1 with the latest updates applied.

  • Review the Release Notes

  • Plan the upgrade order and follow it.

  • You must upgrade the appliances in order of dependency upon each other.

    1. Shut Down Order: Prepare a list of your appliances that defines the correct shut down order:

      • TeamWorks: All TeamWorks appliances must be shut down first.

      • TeamWorks Search: Next, you shut down the TeamWorks Search appliances.

      • PostgreSQL (if applicable): Finally, if you are using a PostgreSQL appliance instead of an in-house SQL server, you shut it down last.

    2. Deployment Order: Prepare a second list that defines the correct upgrade and deployment order:

      • PostgreSQL (if applicable): If you are using a PostgreSQL appliance instead of an in-house SQL server, you must upgrade and deploy that appliance first.

      • TeamWorks Search: You must upgrade and deploy all of the TeamWorks Search appliances before the TeamWorks appliances.

      • TeamWorks: When the upgraded PostgreSQL and TeamWorks Search appliances are up and running, upgrade and deploy the first TeamWorks appliance. Then upgrade and deploy the additional TeamWorks appliances.

    3. If there are things you need to remember about individual appliances, include those reminders in the appropriate list.

    4. Use the shut down list as you complete the steps in Upgrading the VMs.

    5. Use the upgrade list as you complete the steps in Deploying the Upgraded (Replacement) VMs.

  • Ensure that the VM host has enough unformatted disk space.

  • The VM host server must have enough unallocated disk space to contain the following disks for each appliance. This is only temporary because after the upgrade completes, old appliances can be deleted and their disk space reclaimed.

    • System Disk (/): This is created automatically as you deploy the downloaded software.

      Size is 20 GB per appliance.

    • Disk 2 (/vastorage): You make a copy of each old appliance’s Disk 2.

      Size needed equals the total size of all disks to be copied.

    • Disk 3 (/var): You create this disk for each appliance in conjunction with the upgrade process.

      Size recommendation for TeamWorks is 4 GB plus 3 times the RAM allocation for each appliance being upgraded.

    NOTE:The existing /vashare mount point is used by the upgraded TeamWorks appliances. No new disk space is required for upgrading.

  • Remove all VMware Snapshots

  • Before copying Disk 2, make sure to remove all VMware snapshots so that the /vastorage disk has the correct disk file and latest configuration settings.

  • Make sure that upgraded appliances meet TeamWorks system requirements.

  • Do not attempt unsupported path migrations.

  • No Mixed Versions: All of the TeamWorks and TeamWorks Search appliances in an multi-appliance deployment must be upgraded to the same version.

  • No Cross-Deployment-Types: You can only upgrade all-in-one to all-in-one or multi-appliance to multi-appliance.

    If you have an all-in-one deployment, and you need a multi-appliance deployment, you must either install a new system or contact Micro Focus Consulting to assist you with the migration.

  • Prepare appliances with two network adapters before upgrading.

  • For any appliances with two network adapters, do the following:

    1. Download the networkprep.zip file from the TeamWorks software downloads page.

    2. Enable SSH on the appliance, as described in Managing System Services in the TeamWorks 18.2: Administrative UI Reference.

    3. Using an SSH client (such as WinSCP), log in to the appliance as the root user.

    4. Copy the networkprep.zip file that you downloaded to the /root/ directory on the appliance.

    5. Unzip the networkprep.zip file:

      unzip networkprep.zip

      The networkprep folder is created.

    6. Change to the network prep folder:

      cd /root/networkprep

    7. Run the script:

      sh run-networkprep.sh

    8. Close the remote SSH connection to the appliance.

  • Plan when to upgrade.

  • TeamWorks services must be offline during the upgrade.

    1. Schedule the upgrade for a block of time that is least disruptive from a production standpoint.

    2. Notify TeamWorks users in advance of the upgrade so that they have time to prepare.

After ensuring that you have met the prerequisites and cautions above, complete the instructions in the following sections in order.