Upgrading SkySync is relatively simple and you should be prompted automatically every time you restart the user interface when there is an update pending. As a general rule we release an update about once a month with a major releases every 6 months. If you have a specific upgrade schedule regarding your SkySync installation please be aware all bugs will only be addressed by our support on the latest version

When preparing to upgrade a SkySync instance, we recommend the backup of important configuration files in case of corruption during the upgrade. Failure to perform this backup may result in loss of data during recovery.

Backing up SkySync Core Configuration Files

Default installation directories

C:\ProgramData\PortalArchitects

C:\Program Files (x86)\SkySync

1) Backup all of the files with the ".config" file extension within "\Program Files (x86)\SkySync" folder

appsettings.config
connections.config
migrate.exe.config
skysync.exe.config
skysyncservice.exe.config

2) Under the folder "\ProgramData\PortalArchitects\" backup the entire data folder if you are using SQL CE as it contains your CE database or just the nested keys folder if you are using SQL Express or Full SQL.

3) If using SQL Express of Full SQL Server make a back-up of the database.

Single Node Upgrade

1. When opening SkySync you should receive a prompt to download the newest version

2. Clicking yes will download the upgrade, close SkySync, and immediately begin installing upgrade once the download is complete.

3. Click next or Upgrade depending on your installation

Depending on the install you may be prompted to confirm some information. Example of this is the Windows User ID if the non authenticated user option is being used

4. Once the upgrade is completed re-open SkySync to confirm functionality

Windows Defender Warning

It is possible when installing SkySync, that you will receive a message from Windows Defender blocking the install. This message can be manually bypassed by expanding the More Info.

Expand for more information and image

This is not a cause for alarm and should stop happening in the near future. Some of our newer features resulted in the security system identifying us as a potential threat in their latest versions. Unfortunately we do not have a time frame for when the warning will stop occurring, but as mentioned it should not be the cause for alarm.

Multi node upgrade

Never have two different versions of SkySync connected to the same Database. Periodically we will adjust the database schema and if two versions with different schemas are connected to the same database it can corrupt it. The steps below go over the specific process required to prevent this from occurring. Each cluster should be upgraded separately.

The Cluster

The process described below pertains to the cluster being upgraded. This must occur before the steps regarding the Nodes are started.

1.Close and re-open the application on any node. You will be prompted to download the updated software installer. Select "Save for later" and download the installer. You can then copy the installer to each node, or repeat this step on each node and download separately.

Do not run the installer until step 2 has been completed as this can result in corruption.

2. Stop the SkySync service on every node in the cluster.

If you have an application that will automatically restart services then the SkySync service will need to be disabled as opposed to simply stopped.

The Nodes

1. Run the installer on the first node.

Depending on the install you may be prompted to confirm some information. Example of this is the Windows User ID if the non authenticated user option is being used

2. Restart the application to ensure connectivity to the job service.

3. Repeat this process on every node within the cluster.

When preparing to upgrade a SkySync instance, we recommend the backup of important configuration files in case of corruption during the upgrade. Failure to perform this backup may result in loss of data during recovery.

Backing up SkySync Core Configuration Files

C:\ProgramData\PortalArchitects

C:\Program Files (x86)\SkySync

1) Backup all of the files with the ".config" file extension within "\Program Files (x86)\SkySync" folder

appsettings.config

connections.config

migrate.exe.config

skysync.exe.config

skysyncservice.exe.config

2) Under the folder "\ProgramData\PortalArchitects\" backup the entire data folder if you are using SQL CE as it contains your CE database or just the nested keys folder if you are using SQL Express or Full SQL.

3) If using SQL Express of Full SQL Server make a back-up of the database.

Single Node Upgrade

1. When opening SkySync you should receive a prompt to download the newest version

2. Clicking yes will download the upgrade, close SkySync, and immediately begin installing upgrade once the download is complete.

3. Click next or Upgrade depending on your installation

Depending on the install you may be prompted to confirm some information. Example of this is the Windows User ID if the non authenticated user option is being used

4. Once the upgrade is completed re-open SkySync to confirm functionality

Windows Defender Warning

It is possible when installing SkySync, that you will receive a message from Windows Defender blocking the install. This message can be manually bypassed by expanding the More Info.

Multi node upgrade

The Cluster

The process described below pertains to the cluster being upgraded. This must occur before the steps regarding the Nodes are started.

1.Close and re-open the application on any node. You will be prompted to download the updated software installer. Select "Save for later" and download the installer. You can then copy the installer to each node, or repeat this step on each node and download separately.

Do not run the installer until step 2 has been completed as this can result in corruption.

2. Stop the SkySync service on every node in the cluster.

If you have an application that will automatically restart services then the SkySync service will need to be disabled as opposed to simply stopped.

The Nodes

1. Run the installer on the first node.

Depending on the install you may be prompted to confirm some information. Example of this is the Windows User ID if the non authenticated user option is being used

2. Restart the application to ensure connectivity to the job service.

3. Repeat this process on every node within the cluster.

Browser not supported