...

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.

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.