...
- Download & extract the new build,
- Import in settings from the old build to new build,
- (Migrate any data, if a schema change has occurred- we will let you know of supported upgrade paths and whether any of them will involve any schema changes),
A schema describes the structure of an application database, ie: tables, data types, views, stored procedures, etc. If a schema change has occurred, this means the way the application represents your data has changed and will need converted to the new data representation model. - Stop the syndeia-cloud service from the old build,
- Start the syndeia-cloud service from the new build.
...
Upgrading Syndeia Cloud
...
Download and extract new build
...
1. Download the new build,
...
5. Are schema changes being introduced? If No, proceed to the next step. If Yes, skip the next step.
...
A. Upgrade with no Schema Changes
...
6. Stop the syndeia-cloud service for the old build.
...
9. Validate it’s working by proceeding to Validating Build and if successful, skip the remaining steps below, otherwise, fall back to the old build and triage why the new build is not working until it is.
...
B. Upgrade with Schema Changes (migrate data)
...
10. Define a new keyspace for the new build, call it something different from the old build’s keyspace, ie: syndeia_new (see Appendix B2.7 on how to create a keyspace),
...
20. Restart the syndeia-cloud service. Validate it’s working by proceeding to Validating Build. If successful, perform any other data-specific tests and either keep or delete the previously created backup/export now, or after a period of time you are comfortable with (ex: 1-2 weeks).
...
Validating Build
...
21. Follow the validation steps provided in the Validating Syndeia Cloud Installation & Configuration section.