/
Upgrading with Syndeia Automated Deployment (3.7 -> 3.7.1)

Upgrading with Syndeia Automated Deployment (3.7 -> 3.7.1)

This section describes the process for upgrading from Syndeia Cloud 3.7 to Syndeia Cloud 3.7.1.

 

Overview

Please read the following carefully before proceeding.

  1. The upgrade process described in this document applies to Syndeia Cloud 3.7. If you are running 3.6, 3.6 SP1, or 3.6 SP2 you must first upgrade to 3.7 before proceeding. Detailed steps for this are available in the Upgrade (3.6 SP2 -> 3.7) section.

  2. Source and Target Server Terminology - This document describes a side-by-side (parallel) upgrade process, involving two servers:

    • Source Server: The original server running Syndeia Cloud version 3.7.

    • Target Server: The cloned server, which will be upgraded to Syndeia Cloud 3.7.1.

  3. The estimated time to complete the upgrade process excluding server cloning and file transfer time, is approximately 2-3 hours. During this period, end users should not access the original Syndeia Cloud server (3.7). Only administrators should have access during the upgrade.

  4. Migration Process Overview

    • Stages 1-2: The existing Syndeia Cloud 3.7 production environment is cloned to create a new environment, which will serve as the basis for Syndeia Cloud 3.7.1 Before cloning, ensure that the Syndeia Cloud 3.7 deployment is unavailable to users. The original 3.7 production server can be brought back online after cloning, but note that any data created in the original environment after this update will not be migrated automatically or during this process. This ensures the existing deployment remains as a reliable fallback for the migration process.

    • Stages 3-4: Syndeia Cloud 3.7.1 installation files are downloaded and uploaded to the target server, which is then prepared for the upgrade.

    • Stage 5: The Syndeia Cloud 3.7.1 services are started, and data is verified. The new cloned environment is now your Syndeia Cloud 3.7.1 production environment.

  5. All pre-requisites must be met for the target Syndeia Cloud instance. Please refer to the Automated Deployment for details.

  6. Sample outputs are shown in Expand sections throughout this document. You can view the expected output for a given command by clicking the “<“ symbol in the expand section. You can try it out in the example expand section below:

This is an example of fixed-width formatted output

Scope and Limitations

This document outlines the process for upgrading a single-node Linux-based Syndeia Cloud environment. Specific instructions for multi-node environments and Windows-based installations are outside the scope of this document.

Multi-node Environments

Due to the variability in multi-node setups, instructions for upgrading multi-node installations are not provided here. Users with experience managing their multi-node environments may adapt the instructions as needed. For additional help with multi-node environments, users can open a request on our helpdesk.

Windows Server-based Environments

Windows Servers are not proper servers for Syndeia Cloud 3.7.1. Syndeia uses latest versions of IT, such as Cassandra, and those services' communities support Linux distributions. This is necessary for expanding Syndeia capabilities and for enhanced cybersecurity. Specifically, Syndeia Cloud 3.7 requires Cassandra 4.1 and these later Cassandra versions are no longer supported, by Datastax and others, on Windows Servers.

Syndeia admins running Syndeia Cloud on Windows Server are encouraged to open a request on our helpdesk and get our assistance on a path forward.

Refer to the following page for additional details: Other Notes - Windows Server Support.

Offline Mode

Customers operating in an air-gapped environment requiring an offline mode installation can do so by following the preparation steps outlined in the Offline / Air-Gapped Deployment document. Once those steps are followed, the remainder of the stages outlined in this document should be the same. If any issues or questions arise relating to this offline installation mode, please submit a help ticket.

The Syndeia Cloud 3.7 → 3.7.1 migration process has the following stages.

We describe the simple process to deploy a service patch release for classic VM deployment here.