Versions Compared

Version Old Version 10 New Version Current
Changes made by

Peter Ransom (Deactivated)

Chad Glitz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Section


Column
width75%

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.


Column
width25%




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 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.

...

4) Restore the SQL database on the new server 

Note

If SkySync is not being moved

and therefore

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.


Info

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.

...

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.

Note

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.