Page Comparison

We are glad that you are reading this page because that means you’re already convinced of the power of Syndeia 3.3 with all the cool, new features and you’ve either already installed Syndeia Cloud 3.3, or are in the process of doing so, and you are wondering what happens to the data that you’ve painstakingly created with Syndeia Cloud 3.2? Well, since Syndeia 3.3 was such a big release, a lot has changed behind the scenes, and that means, unavoidably, you’ll have to migrate your data so that it complies with the data format expected by Syndeia 3.3. This page explains what the entire migration process entails and the steps to successfully transition to Syndeia 3.3.

NOTE: For the remainder of the document, whenever Syndeia 3.3 is mentioned, it means Syndeia Cloud 3.3, and same for Syndeia 3.2.

...

1. Syndeia 3.2 installed and running on a server. Syndeia 3.2 requires the Cassandra database and a syndeia keyspace to hold 3.2 data. This is our source server (database).

2. Syndeia 3.3 installed and running on a server. Syndeia 3.3 also requires the Cassandra database and syndeia_cloud_store & syndeia_cloud_auth keyspaces to hold 3.3 data. Additionally, Syndeia 3.3 uses JanusGraph behind the scenes, which requires additional syndeia_cloud_graph & syndeia_cloud_graph_config keyspaces to hold graph data. This is our target server (database).

3. The superuser and the setup steps should’ve already been run on the Syndeia 3.3 server.

4. The migration process requires an additional syndeia_cloud_devops keyspace on the target 3.3 server. This keyspace has three sets of tables - a pre_stage_* set, a migrate_stage_* set, and a duplicate_* set of tables.

5. The Syndeia-Migration-3.3 utility.

6. The user who is doing the migration should be an admin user. Additionally, he should have the credentials of each external repository (server) because one of the steps requires that you run the Syndeia dashboard and connect to each of the repositories using your credentials. Also, this user should have permission to view all the data in any of the external repositories (servers).

...

Step 1 - Replicate all data from Syndeia Cloud 3.2

...

2

...

...

bin\syndeia-migration.bat -r All

...

Step 2 - Enhance and Stage Users

bin\syndeia-migration.bat -e Users -s Users

Step 3 - Migrate users

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=user

Step 4 - Enhance repository, container and relation types

bin\syndeia-migration.bat -e RepositoryTypes

bin\syndeia-migration.bat -e

...

ContainerTypes

bin\syndeia-migration.bat -e RelationTypes

Step 5 - Stage repository and relation types

bin\syndeia-migration.bat -s RepositoryTypes

bin\syndeia-migration.bat -s

...

RelationTypes

Step 6 - Enhance and stage repositories

...

bin\syndeia-migration.bat -e Repositories -s Repositories

Step 7 - Migrate repositories

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=repository

Step 8 - Launch the Syndeia dashboard and connect to each of the repositories using (admin) credentials, or the user should have access to all the data in any of the external repositories (servers).

Step 9 - Enhance containers and stage container types & containers

...

bin\syndeia-migration.bat -e Containers

bin\syndeia-migration.bat -s ContainerTypes

...

bin\syndeia-migration.bat -s Containers

Step 10 - Migrate container types & containers

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=containertype

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=container

Step 11 - Enhance artifacts and stage artifact types & artifacts

...

bin\syndeia-migration.bat -e Artifacts

bin\syndeia-migration.bat -s ArtifactTypes

...

bin\syndeia-migration.bat -s Artifacts

Step 12 - Migrate artifact types & artifacts

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=artifacttype

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=artifact

Step 13 - Enhance and stage relations

...

bin\syndeia-migration.bat -e Relations -s Relations

Step 14 - Migrate relations

bin\devops.bat -Dsyndeia.client.action=migrate -Dsyndeia.migrate.schema=relation