Migration

Owned by Peter Ransom (Deactivated)
Last updated: Oct 31, 2017 by Chad Glitz

The processes and scenarios in this article provide instructions on how to move a SkySync or SQL node from one server to another. If migrating multiple SkySync nodes the process explained below will need to be repeated on each one. If migrating multiple clusters, then the migration should be done one cluster at a time.



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 on every node accessing the SQL database. 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 SQL login ID's after the transfer as you where before. If this is not the case SkySync will need to be reinstalled to utilize the new logins.

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 the SkySync service should be stopped to prevent additional information being written on the old database. Also any other programs that access the SQL database should be stopped while the migration is occurring. 

1) Stop the SkySync Service on every node accessing the SQL database. 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 or 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 SQL 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 and place it in a folder on the desktop. 

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

3) Ensure that the SkySync service has been stopped on the old 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

13) Once the installation is complete copy the old Keys folder to the directory C:\ProgramData\PortalArchitects\Data on the new computer.

The directory C:\ProgramData\PortalArchitects\Data is the default location but can be adjusted during installation.


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. Follow the processes above first for moving a SQL Database and then for Reinstalling SkySync.

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

When the SQL server is being upgraded and it is located on a separate server from SkySync then it is not necessary to move the SkySync installation. As with any scenario the SkySync service should be stopped, and actions effecting the SQL database should be halted. After SQL has been moved 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. Follow the process above for Moving SQL to a different server.

As mentioned above if the SQL login user ID is changed SkySync will need to be uninstalled and reinstalled in order to connect to the new SQL database.

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

When upgrading just the SkySync node only SkySync will need to be migrated and no action needs to be taken on the SQL server. 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. Follow the process above for re-installing SkySync.