Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update refs of "3.4-SP3 -> 3.5 SP2" to now "3.5 SP2 -> 3.6"

This section describes the process for migrating from Syndeia Cloud 3.4 SP3 5 SP2 to Syndeia Cloud 3.5 SP2 (the latest service pack)6. In the remainder of this document, Syndeia 3.6 5 implies Syndeia 3.6 5 SP2.

Overview

Please read the following carefully before proceeding further.

(1) The starting point of the migration process is Syndeia Cloud 3.4 SP3. If you are currently running 3.4 5 / 3.4 5 SP1 / 3.4 SP2, please first upgrade to 3.4 SP3 5 SP2 then return here. The process is described in 3.4 Service Pack 3 (3.4 SP3)

...

  • Stages 1-2 – The existing Syndeia 3.4 SP3 5 SP2 environment running in production is cloned to create a new environment that is the basis for Syndeia Cloud 3.5. Syndeia admins should make the Syndeia Cloud 3.4 SP3 5 SP2 production deployment unavailable to Syndeia users before cloning. Syndeia 3.4 SP3 5 SP2 production server can be brought back online after cloning but any data created in it after cloning will not be migrated. This approach is taken to ensure that the existing Syndeia Cloud 3.4 SP3 5 SP2 deployment is always available as a golden starting point for the migration process.

  • Stages 3-6 – Syndeia Cloud 3.5 6 installs are downloaded, services are started, and an upgrade is performed in the cloned environment.

  • Stage 7-10 - Syndeia Cloud 3.5 6 infrastructure services (Cassandra, JanusGraph, Zookeeper, Kafka) are upgraded to the latest/newer versions in the cloned environment. This is required for: (1) new capabilities in Syndeia Cloud 3.56, and (2) cybersecurity hardening of the Syndeia Cloud system.

  • Stages 11-12 – Syndeia Cloud 3.5 6 services are started and the data is verified. The cloned environment is now the new Syndeia Cloud 3.56-based production environment.

...