-
Notifications
You must be signed in to change notification settings - Fork 5
Upgrade
After the COMET Server has been installed, it may be that new versions are released and that an upgrade is required. Depending on your deployment, whether it is docker based or not the procedure is slightly different.
- Check whether your PostgreSQL setup is the latest supported version, currently this is version PostgreSQL version 16.x. Previous versions will still work, but we advise you to upgrade to the most recent version of PostgreSQL that CDP4-COMET supports.
- Create a backup of your database using
pg_dumpall
; we hope you are doing this frequently - Update the Docker-Compose file by updating the tag of the
comet_webservices
docker imagestariongroup/comet-webservices-community-edition:8.x.y
- Restart the services using Docker-Compose
Note: The COMET Web Services will make any required updates to the database (schema changes) when it starts.
- check whether your PostgreSQL setup is the latest supported version, currently this is version PostgreSQL version 16
- stop the COMET Web Service:
service cdp4-web-services stop
- Create a backup of your database using
pg_dumpall
; we hope you are doing this frequently - Download the latest release of the COMET Web Services
- Replace the files located in the
/opt/comet/midtier/nancyfx
folder (and subfolders) using the updated files from the distribution. You will need to replace the.dll
and.exe
files. Make sure you keep your configuration files, you will still need them. - start the CDP4 Web Service:
service comet-web-services start
Note: The COMET Web Services will make any required updates to the database (schema changes) when it starts.
More information coming soon
CDP4-COMET has been upgraded to support version 16.x of PostgreSQL. In case you are upgrading from a previous major release (9.x, 12.x , etc.) some extra work is required. The way that PostgreSQL stores the files on disk is incompatible between major versions. In case you want to upgrade between major versions there are 2 ways to achieve this:
- logical upgrade using pg_dumpall and pg_restore
- using the
pg_upgrade
command to update the files PostgreSQL stores on disk. - streaming replication between a primary and secondary PostgreSQL server.
Unless streaming replicaton is used, it is best to perform this by disabling the CDP4-COMET WebServices during a maintenance window to make sure there are no intermediate updates made on the server by your users.
More information coming soon
Please follow these steps:
- stop the COMET Web Service:
service comet-web-services stop
- Create a backup of your database using
pg_dumpall
; we hope you are doing this Backups. The resulting sql dump will be used to seed the new PostgreSQL 16 cluster - follow the PostgreSQL version 16 installation instructions
- Initialize a new PostgreSQL cluster using these instructions. Instead of downloading the
cometserver.sql file
to initialize the CDP4-COMET Database, make use of the sql dump created in an earlier step. Make sure that your new cluster is not listening on the same port as your existing cluster. - update the
appsettings.json
to point to the new PostgreSQL cluster
copyright @ Starion Group S.A.