Difference between revisions of "AquilaServer New Install and Migration"

From EHS Help
Jump to: navigation, search
m
Line 2: Line 2:
 
==AquilaServer Migration==
 
==AquilaServer Migration==
  
The following steps are to migrate AquilaServer from one server to another, whilst the database remains static.
+
The following steps are to migrate AquilaServer from one server to another.
  
* Stop and disable existing aquilaserver service to prevent further user access.
+
This assumes your database is stored on a different machine to the server app.
* Install aquilaserver on new server. For further details please see [[Aquila Server Installation]]
+
 
* Copy the `AquilaServer.ini` file from the old server installation directory, to the new, in order to easily preserve your settings.
+
* Make a copy of the `AquilaServer.ini` file from the old server installation directory, so you retain your current settings information.
* Uninstall aquilaserver from the old server.  
+
* Install aquilaserver on new server
 +
** The installation will ask for the name of the SQL Server and Database, and for the SQL Server Login information.
 +
** Input the requested information into the installer using the information in the `AquilaServer.ini` file, from the line `ConnectionString=....`
 +
*** If your Connection String has no user id or password, but has "Integrated Security=SSPI" - simply leave the user id and password fields blank.
 +
** For further installation details please see [[Aquila Server Installation]]
 
* Distribute the new server URL to your users, where it can be updated on the login screen.
 
* Distribute the new server URL to your users, where it can be updated on the login screen.
  
==Database Migration==
+
When the new installation is confirmed and working:
 
+
The following steps are for migrating your database whilst keeping the application server in the same location:
+
 
+
* Ensure new server has SQL Server installed and available
+
* If you're using SQL Server Logins; create a new login for the AquilaServer service to connect that matches your previous installation. For more info please see [[Creating a SQL Server Login]].
+
* Stop the Aquilaserver service on the application server to prevent user access.
+
* Backup database on old server
+
* Transfer & restore database to new server
+
* Edit the aquilaserver.ini file in the installation folder on the application server to reflect the new database location
+
* Restart the AquilaServer service.
+
* AquilaCRS client re-configuration is not necessary.
+
 
+
==AquilaServer and Database Migration==
+
 
+
It is recommended to migrate one component at a time & ensure the system is fully functioning and then migrate the other component.
+
 
+
E.g. migrate the database first, ensure the system works & then perform the AquilaServer migration steps.
+
  
If you have a single server running both AquilaServer and the Database you should also migrate one component at a time to the new server.
+
* Uninstall aquilaserver from the old server.

Revision as of 10:05, 18 May 2020

AquilaServer Migration

The following steps are to migrate AquilaServer from one server to another.

This assumes your database is stored on a different machine to the server app.

  • Make a copy of the `AquilaServer.ini` file from the old server installation directory, so you retain your current settings information.
  • Install aquilaserver on new server
    • The installation will ask for the name of the SQL Server and Database, and for the SQL Server Login information.
    • Input the requested information into the installer using the information in the `AquilaServer.ini` file, from the line `ConnectionString=....`
      • If your Connection String has no user id or password, but has "Integrated Security=SSPI" - simply leave the user id and password fields blank.
    • For further installation details please see Aquila Server Installation
  • Distribute the new server URL to your users, where it can be updated on the login screen.

When the new installation is confirmed and working:

  • Uninstall aquilaserver from the old server.