Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


SQL database needs to be changed in connections.config file

The below processes are for SQL Express and Full SQL only, and are not relevant to SQL CE.

Before any actions are taken, SkySync Files should be backed up to a folder on the desktop to prevent loss of connections and configurations

C:\Program Files (x86)\SkySync\appSettings.config

C:\Program Files (x86)\SkySync\connections.config

C:\ProgramData\PortalArchitects\Data\Keys

To prevent discrepancies between the SQL Servers the SkySync Service will need to be stopped. If any programs are in place that automatically start the SkySync service they will need to be disabled. All activity on the SQL database should also be avoided until the migration is complete to prevent database discrepancies.

The process of transferring the SQL database will depend on your individual setup. The setups below assume that you are using the same login ID's after the transfer as you where before. If you are not using the same login ID's then their ability to connect to SQL should be tested prior to beginning the process. This is because SkySync will not be able to be re-installed if they cannot connect. 

Scenario 1: SQL and SkySync are located on the same server and need to be moved to a new server

In this scenario SkySync and the SQL Database are located on the same Server or Virtual Machine, and need to be moved to a new server. To do this the SQL database will need to be moved, and SkySync will also need to be reinstalled on the new server with a custom install. Additionally the Keys folder located at C:\ProgramData\PortalArchitects\Data\  will also need to be moved from the old server to the new one. The processes below go over Moving SQL and reinstalling SkySync and should be followed as necessary.


Scenario 2: SQL and SkySync are installed on two separate Servers and only SQL needs to be moved

This scenario is most common with an SQL or server upgrade, resulting in the requirement of migrating SQL but not SkySync. As with any scenario the SkySync service should be stopped. After this the SQL Database will need to be moved to the new server. As long as the user IDs remain the same as they where before the migration SkySync will not need to be reinstalled. If however, the user IDs are changed then SkySync will need to be reinstalled. In the case where a reinstall is not necessary, simply edit the connections.config file located in C:\Program Files (x86)\SkySync to reflect the new SQL server name and restart the SkySync service. 

Scenario 3: SQL and SkySync are installed on two separate Servers and only SkySync needs to be moved

This scenario is most common a upgrade is occurring resulting in SkySync needing to be reinstalled on a new server/node. As with anytime a migration of any type is taking place it is important to stop activity on the database as well as stop the SkySync service. It is also necessary to move a copy of the Keys folder located at C:\ProgramData\PortalArchitects\Data\ to the new server. After this is done simply reinstall SkySync using the most recent installer on the new server being sure to use the custom install so that the SQL server can be specified. Once SkySync has been reinstalled copy the keys folder into the path C:\ProgramData\PortalArchitects\Data overwriting the folder that will have been created automatically. 

Moving SQL to a different server

The recommended method of moving the SQL databases is to perform a backup on the Source Database and a restore on the Destination database. Before this is done however the SkySync service should be stopped to prevent additional information being written on the old database. It should be kept in mind that SQL databases can still be accessed during the backup process and it is advised to have all users cease access while the migration is being performed. 

1) Stop the SkySync Service. If there are any programs which automatically start stopped services they will need to be disabled

2) Stop activities that access the SQL Database 

3) Backup the SQL database and move it to the new server

4) Restore the SQL database on the new server 

If SkySync is not being moved and therefore reinstalled, the connections.config file located at C:\Program Files (x86)\SkySync will need to be adjusted to reflect the new SQL Server and database.

This Microsoft support article explains how to transfer databases in greater detail and can be used for reference if needed additionally individual articles on backup and restore have been added below.

For Steps on how to backup a SQL database see this Microsoft support article here.

For Steps on how to restore a SQL database see this Microsoft support article here.


Re-installing SkySync

In order to install SkySync you will need access to the latest installer, please contact support for a link or copy of it. 

1) Copy the Keys folder located in C:\ProgramData\PortalArchitects\Data from the source server to the new server. 

2)Download and extract the newest installer on the new server.

3)Double-click the SkySync.exe to begin the installation

4) Check the box to accept the terms and select Custom install before clicking next

5) Click next

6) Local System account is an option however it is recommended to select a specific Windows account created for SkySync login

7) Click Next

8) Select SQL Server from the drop down menu

9) Select or type the name of the SQL server 

10) Input the User Name and Password

11) Click Validate

12) Click Next

Once the installation is complete copy the old Keys folder to C:\ProgramData\PortalArchitects\Data on the new computer and overwrite anything that is already there.

To confirm that everything is working properly SkySync should be opened and it should be confirmed that the jobs and connectors before the move are still there.

  • No labels