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.
| Warning |
|---|
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 configurationsC:\Program Files (x86)\SkySync\appSettings.configC:\Program Files (x86)\SkySync\connections.configC:\ProgramData\PortalArchitects\Data\KeysTo 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. |
| Note |
|---|
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. |
...
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
...
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 a 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.
...
Follow the process above for Moving SQL to a different server.
Scenario 3: SQL and SkySync are installed on two separate Servers and only SkySync needs to be moved
This scenario
...
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
...