Difference between revisions of "AquilaServer New Install and Migration"
From EHS Help
m (→Application Server Migration) |
m (→Database Migration) |
||
| Line 10: | Line 10: | ||
==Database Migration== | ==Database Migration== | ||
| − | * | + | * Ensure new server has SQL Server installed and available |
| − | * Stop | + | * Create a new login for the AquilaServer service to connect with, unless using integrated authentication. 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 | * Backup database on old server | ||
* Transfer & restore database to new server | * Transfer & restore database to new server | ||
| − | * Edit the aquilaserver.ini file on the application server to reflect the new database location | + | * Edit the aquilaserver.ini file in the installation folder on the application server to reflect the new database location |
| − | * Restart the AquilaServer service. | + | * Restart the AquilaServer service. |
| − | + | * AquilaCRS client re-configuration is not necessary. | |
==Database and Server Migration== | ==Database and Server Migration== | ||
Revision as of 15:21, 7 March 2019
Application Server Migration
- Stop and disable existing aquilaserver service to prevent further user access.
- 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.
- Uninstall aquilaserver from the old server.
- Distribute the new server URL to your users, where it can be updated on the login screen.
Database Migration
- Ensure new server has SQL Server installed and available
- Create a new login for the AquilaServer service to connect with, unless using integrated authentication. 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.
Database and Server Migration
- Install SQL server on new server (if not already) but do not create database. Create a new login for AquilaServer (unless using integrated authentication. For more info please see Creating a SQL Server Login).
- Stop and disable existing aquilaserver service to prevent further user access.
- Backup database on old server
- Transfer & restore database to new server
- Install aquilaserver on new server. For further details please see Aquila Server Installation
- Configure aquilaserver with the database connection. For further details please see Aquila Server Installation
- Update each client with the new server URL (via the F2 option on login screen)
