Upgrading to a new major version (for example, upgrading from 2024 to 2025) requires new product keys to license the application. You can request new keys from Sales (sales@.com).
Upgrading 2025 to a Newer Build
2025 is shipped in a setup.exe file for Microsoft Windows and in a compressed .tar.gz file for Linux. Follow the steps for your operating system to upgrade an existing installation of 2025 to a newer build.Microsoft Windows
- Stop the server via Windows Services Manager.
- Run setup.exe.
- Point the installer to the location where is installed.
- Restart the server as a service after the upgrade is completed.
Linux
-
Stop the server in either of the following ways:
-
To stop the server as a service, submit this command:
sudo systemctl stop cdatasync -
To stop the service in-process, submit this command:
java -jar sync.jar -stop
-
To stop the server as a service, submit this command:
-
Unzip the sync.war file from the tar.gz archive and place it in the
/opt/sync/webapp/directory. Unzipping the file in this location overwrites the old file. -
(Optional) Unzip the sync.jar file from the tar.gz archive and place it in
/opt/sync/. Unzipping the file in this location overwrites the old file. -
Start the server in either of the following ways:
-
To start the server as a service, submit this command:
sudo systemctl start cdatasync -
To start the service in-process, submit this command:
java -jar sync.jar
-
To start the server as a service, submit this command:
-
No matter how you choose to deploy , the files and folders that are contained in
ApplicationDirectorymust be readable and writable by the user who runs the application. The service.sh script that is included with uses cdatasync as this user. -
If the application was previously run as a different user and you want to restore the necessary permissions for a cdatasync user to run the application, submit a command that is similar to the following:
sudo chown -R cdatasync:cdatasync /opt/sync
Upgrading from 2020-2024
This section explains how to upgrade from 2020, 2021, 2022, 2023, or 2024 to 2025.Cross-Platform Edition
2025 is shipped in a setup.exe file for Microsoft Windows and in a compressed .tar.gz file for Linux. Follow the steps for your operating system to upgrade an existing installation of to 2025.Microsoft Windows
- Stop the server via Windows Services Manager.
- Run setup.exe.
- Point the installer to the location where is installed.
- Restart the server as a service after the upgrade is completed.
Linux
-
Stop the server in either of the following ways:
-
To stop the server as a service, submit this command:
sudo systemctl stop cdatasync -
To stop the service in-process, submit this command:
java -jar sync.jar -stop
-
To stop the server as a service, submit this command:
-
Extract the contents of .tar.gz to
/opt/sync/. -
Submit the following upgrade command only if you are upgrading from 2021 or earlier. Otherwise, continue to step 4.
sudo bash /opt/sync/upgrade.shOptional: You can specify the-InstallDirectoryparameter if your previous installation uses a nondefault path. -
Start the server in either of the following ways:
-
To start the server as a service, submit this command:
sudo systemctl start cdatasync -
To start the service in-process, submit this command:
java -jar sync.jar
-
To start the server as a service, submit this command:
-
No matter how you choose to deploy , the files and folders that are contained in
ApplicationDirectorymust be readable and writable by the user who runs the application. The service.sh script that is included with uses cdatasync as this user. -
If the application was previously run as a different user and you want to restore the necessary permissions for a cdatasync user to run the application, submit a command that is similar to the following:
sudo chown -R cdatasync:cdatasync /opt/sync
.NET
Starting with 2024, the .NET edition of the application is deprecated. As a result, you need to migrate your current .NET edition of to the Cross-Platform edition. Follow these steps to perform this migration:- If you use the default SQLite application database, you must export your settings and then re-import them when you start the Cross-Platform edition of . The Cross-Platform edition does not support SQLite as an application database. It uses the Apache Derby database, by default. You can export your settings from the Migrations tab on the Settings page in . Simply click Export to download all your jobs, connections, and settings into zipped CSV files.
- (Optional) Rename the .NET application folder so that the new Cross-Platform edition will be installed in a separate folder.
-
Download and install the Cross-Platform edition from the website. During installation, the new download should overwrite the service definition.
Before you start the server, you need to update the sync.properties file if you are using an external database. You can change the port, change the inactivity (session) timeout, and more in this file. For example, you can change the port by locating the following line in sync.properties and changing the default port (8181) to a port of your choice:
cdata.http.port=8181 - Start the application and install your license from the License tab on the Settings page.
- Import the settings that you exported in step 1.
Upgrading from 2017-2019
The installer for 2025 attempts to detect existing previous installations of and to import previous settings. These imported settings include the following:- All jobs
- All connections
- Any external connectors
- All settings