Versions Compared

Version Old Version 9 New Version 10
Changes made by

Anjali Tyagi

Kyle Miller (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Get Products and Docs

  1. Go to the Downloads section on the DataCore Support Portal.

  2. Scroll down and open the Swarm toggle

    • Whenever a new component version is available (such as a new release of Content Gateway), these bundles are updated and the ZIP file name changes to reflect the release date for the bundle.

  3. From the Documentation Archive page, download the corresponding PDF specific to your bundle. 

    • The comprehensive PDF that matches all of the components at those versions is uploaded to the Documentation Archive using a filename that includes that same release date for its matching bundle.

    • The Swarm online documentation is continually updated to the current release; because the PDF is a snapshot that is tied to a bundle release, consider it the definitive source for that bundle.

    • Our Support team's searchable Knowledge Base contains both technical articles and the very latest documentation, which might be newer than your the installed version. 

  4. Expand your the software bundle. In the top-level directory of the bundle, locate and read the README.txt for the version guidance on using the bundle.

  5. Open the PDF you downloaded for your the bundle and see the Release Notes for each component, which include upgrade instructions as well as changes and watch items.

...

  1. Plan upgrade impacts — Review and plan for this release's upgrade impacts and the impacts for each of the releases since the currently running version you are running. For Swarm 9 impacts, see Swarm Storage 9 Releases.

  2. No volume retires — Do not start any elective volume retirements during the upgrade. Wait until the upgrade is complete before initiating any retires, or ensure that they're complete before upgrading.

  3. Choose your the reboot type — Swarm supports rolling upgrades (a single cluster running mixed versions during the upgrade process) and requires no data conversion unless specifically noted for a particular release. This means that you can upgrade Upgrades are performed without scheduling an outage or bringing down the cluster. Just restart your  Restart the swarm nodes one at a time with the new version and the cluster will continue continues serving applications during the upgrade process. 

    • Rolling upgrade: Reboot one node at a time and wait for its status to show as "OK" in the UI before rebooting the next node. 

    • Alternative: Reboot the entire cluster at once after the software on all USB flash drives or the centralized configuration location has been updated.

  4. Follow your the Upgrade Path, below.

  5. Review the Application and Configuration Guidance.

Upgrade Paths

How you upgrade your Swarm system depends on your Swarm upgrade paths depend on the implementation environment. If you are installing Swarm for the first time, see Installing and Initializing Swarm StorageSee Installing and Initializing Swarm Storage for first time Swarm installations.

Info

Component-only upgrades

Not all components update in every release, so sometimes you might upgrade only ; some upgrades contain a single RPM. Which components you need to upgrade depends on which version you are running. To track component versions, follow The currently running Swarm version determines which components require an upgrade. Follow the release tables on the Documentation Archive to track component versions. 

If you areUpgrade Path options:

...

  1. Running Elasticsearch 2.3.3 or 5.6.12, see Upgrading from Unsupported Elasticsearch, below.

  2. Not using a Search feed or

...

  1. running Elasticsearch 6.8.6, continue with

...

  1. the upgrade path

...

  1. .

CSN

No CSN

  1. Run settings checker and review upgrade impacts

  2. Review and address report with Support

  3. Download the CSN Swarm bundle from the from the Downloads section on the DataCore Support Portal

  4. Upgrade the Storage RPM or run the script (see flowchart)

  5. Select the new Storage version and reboot the cluster to activate it

  6. Standalone Gateway: 

    1. Upgrade Gateway (with Swarm UI, Content UI)

  7. Standalone Elasticsearch: 

    1. Verify that Swarm 14 is working (no downgrading after ES goes to 7)

    2. On ES 6, first install the Search and Metrics RPMs.

    3. Run the config script provided, which installs and configures ES 7:
      configure_elasticsearch_with_swarm_search.py

  1. Run settings checker and review upgrade impacts

  2. Review and address report with Support

  3. Download the Swarm bundle from the from the Downloads section on the DataCore Support Portal

  4. Upgrade Storage (fsimage/kernel files via USB key or PXE server)

  5. Complete required cluster reboot

  6. Standalone Gateway: 

    1. Upgrade Gateway (with Swarm UI, Content UI)

  7. Standalone Elasticsearch: 

    1. Verify that Swarm 14 is working (no downgrading after ES goes to 7)

    2. On ES 6, first install the Search and Metrics RPMs.

    3. Run the config script provided, which installs and configures ES 7:
      configure_elasticsearch_with_swarm_search.py

...

Upgrading from Unsupported Elasticsearch

If you are still Contact DataCore Support to ensure a smooth migration process with no down-time if running unsupported Elasticsearch (versions 2.3.3 or 5.6.12), you will need to work with DataCore Support to ensure a smooth migration process with no down-time.

Swarm 9.6

Gateway 5.4

Elasticsearch 2.3.3

Migration to ES 6.8.6 required
(new cluster and new Search feed)

Swarm 11.3

Gateway 5.4.1

Elasticsearch 2.3.3

Gateway 7.0

Elasticsearch 5.6.12

Elasticsearch 6.8.6

Swarm 14.0

Gateway 7.7

Elasticsearch 6.8.6

Upgrade in-place to ES 7.5.2

Elasticsearch 7.5.2

Upgrade in-place to future ES version

Swarm 14.0 Update 2

Gateway 7.8

Elasticsearch 7.5.2

Upgrade in-place to future ES version

Your The high-level upgrade sequence is as follows:

  1. Swarm 11 bundle:

    1. Upgrade Swarm to 11.3, as guided by Support and the Settings Checker report.

    2. If you are currently using Upgrade to Gateway 5.4.1 if currently running Elasticsearch 2.3.3, upgrade . Upgrade to Gateway 5.4.1. If you are currently using 7.0 if currently running Elasticsearch 5.6.12, you can upgrade to Gateway 7.0. Refer to Upgrading from Gateway 5.x.

    3. Add an Elasticsearch 6 cluster and start a search feed, leaving your the old feed as primary (see Migrating from Older Elasticsearch).

    4. When the feed completes, make it primary.

    5. If you are on Upgrade to Gateway 7.0 if currently running Gateway 5.4.1, upgrade to Gateway 7.0.

    6. Configure gateway.cfg indexerHosts to point to your the new Elasticsearch 6 cluster and restart CloudGateway, using sudo systemctl restart cloudgateway command.

  2. Swarm 14 bundle:

    • Follow the appropriate column in Upgrade Paths, above.
      This is the general order:

      1. Upgrade to Swarm 14.

      2. Upgrade to Gateway 7.7 (from version 5.4.1, follow Upgrading from Gateway 5.x)

      3. Verify Swarm operations (this would be the time to downgrade).

      4. Run the ES config script to upgrade in-place to Elasticsearch 7.

      5. Upgrade Gateway 7.7 to Gateway 7.8.