Subject | sedonaoffice server migrationLog File Cleanup"
|
From | Ryan Farmer |
To | Jeff Mack |
Sent | Friday, January 13, 2017 11:22 AM |
Steps to complete a server migration
(This walkthrough assumes you understand how to create and restore SQL backups and SQL users in SQL Server Management Studio. This walkthrough does not include steps for moving any additional products like SedonaWeb, SedonaSync, or SedonaFSU.)
Your initial step for the migration process will be to set up your new SQL server. Server requirements can be viewed Here. Ensure that you install the default instance (MSSQLSERVER) of your current version of SQL or newer with mixed-mode security and named pipes enabled.
The following applications need to be run on the new server before moving any of the databases and in this order:
SedonaOffice Server installer: http://files.sedonaoffice.com/SedonaOffice_Files/Installation_Files/SOServer5.7.0.0.Rev2.exe 60MB
SedonaOffice Client installer: http://files.sedonaoffice.com/SedonaOffice_Files/Installation_Files/SOClient5.6.8.exe 133MB
------
Once you run the SedonaOffice Server installer you will be prompted to input a license key. Please email the presented Unique Program ID to ITSupport@SedonaOffice.com to obtain your new license key. Once you receive your new license key, copy it to your clipboard, you can select the License button in the Sedona License Activation window and click Paste to input the copied license key.
The full migration process is done in two phases.
Phase One:
This phase consists of backing up all of the SedonaOffice-related databases from the old SQL server and restoring them to the new SQL server. This allows you to test the new server with real data to ensure stability and that there are no unforeseen issues.
Before restoring any databases, you need to delete the MasterSetupCompany, SedonaMaster, and SedonaDocs databases on the new server. These are created by the installer and are not needed.
Restore your backups to the new SQL server. The databases you should be migrating are as follows: SedonaMaster, SedonaDocuments, and any database referenced by the SedonaMaster's Company table.
Once the databases are migrated and restored on the new server, all SedonaUser and SedonaReports SQL users need to be dropped from each database and recreated. The SedonaMaster database's Company table will need to be edited so that the ComputerName and Document_Server columns reflect the new server name.
If the previous databases restored are not current with the SedonaOffice updated version that has been run on the new SQL server, you will need to open the SedonaOffice Client Tools and run the Re-Run Last Update option.
That’s it for Phase One.
Phase Two:
When you have tested out the stability and performance of the new server and you are ready to finish the migration, you can stop the SedonaService on the old SQL Server. This will end all connections to the database from the SedonaOffice application. If you use other products like SedonaSync, SedonaWeb, or SedonaFSU, you can stop the SQL Server Service from ending all connections on the old server.
Create your database backups again, for each of your SedonaOffice-related databases: SedonaMaster, SedonaDocuemnts, and any database referenced by the SedonaMaster's Company table.
Restore the backups to the new SQL Server with the overwrite option allowed, since they already exist.
Once the databases are migrated and restored on the new server, all SedonaUser and SedonaReports SQL users need to be dropped from each database and recreated. The SedonaMaster database's Company table will need to be edited so that the ComputerName and Document_Server columns reflect the new server name and the ConnectionString includes the new server name after "DataSource=".
After all databases are restored, test to ensure you can log into SedonaOffice on the new server.
Any other client installs will need to be adjusted to point to the new server. The easiest way to do this is by exporting a registry key that users can merge into their registries after modifying the server name and SedonaMaster data source server names.
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sedona Development Company\Client
