Yarkon Server – Upgrade

Occasionally, we release software updates, including new features and patches. The simplest method to upgrade your Yarkon Server is to download a new package and replace the existing one with it.

Download the latest version

The FREE Trial is identical to the monthly subscription version. The only difference is in the license key file. Therefore, to get the latest version of Yarkon Server, simply go to the download page and download a new package.

Backup the existing set up

Using the running Yarkon Server, go to the Administration page, the Database tab, and click the Backup button. The system will now download a full backup of your database.

Set up the new server – Side by Side

The recommended way to upgrade systems in the AWS cloud is a “side by side” upgrade, meaning that you set up a new server, verify that it works, then transition the DNS settings to point to the new one, and finally terminating the one that is being replaced. This approach is safe and ensure there is no service interruption to your end users. If you prefer to do an “in place” upgrade, see the below section.

Set up a new server following the same method you used when you set up the existing one. It is usually along the lines described in this document.

Replace the database on the new server

Since you are already setting up a server, the easiest way to proceed is to replace the empty database included in the downloaded package with the backup you just created. The file name is aphek.db and it should be put in the database folder under the root folder of the server.

Start the new server

Start the new server the same way you have set up the existing one. If all goes well, it would identify the database and would run any necessary database migration. Once done, your new server is ready to go.

Update DNS settings

Lastly, you want to put the new server in route, and discard the old one. Depends on your network settings, update the DNS to point to the new server. Once you confirm all functionality is in place, you can safely terminate the old one.

Set up the new server – In Place

The downside of this approach is it might result in service interruption, if there is a problem or an error is made. Otherwise, it is simpler and faster, so you should carefully consider your options.

Shut down the existing server

Depending on the method you set up the application to run, turn it off.

Replace the files

Take the downloaded package as is, and replace the existing files with it, except the database file, which is database/aphek.db. If you happen to remove the database file by mistake, simply use the backup you created before to restore it.

Restart the server

Restart the server. If all goes well, it would identify the database and would run any necessary database migration. Once done, your upgraded server is ready to go.