If you find yourself needing to copy an entire Xtraction installation from a current server to a new server, the process is very straightforward.
Prepare for installation
- Ensure the prerequisites are met on the new server
- Make sure you have the license files for the new server and the installation software for the same version running on the current server
- If users should stop using the current server and start using the new server once it is operational, you should stop the Xtraction application pool on the existing current server to make sure no changes are made by users that would fail to copy to the new server.
Copy the database
- Make a backup of the Xtraction database
- Create a new Xtraction database
- Restore the backup from step 1 into the database created in step 2
- Run through the regular install process of Xtraction on the new server. This should be the same version as found on the current server. The reason to run the install is to add an entry in the registry as installed software, create the start menu shortcuts, and configure IIS.
- During install, just select any adapter. The data model file will be overwritten in a later step.
Copy Xtraction files
- From the current server, copy the 3 Xtraction subfolders (Data, Tools, and Web) on top of the Xtraction subfolders in the new server (this is very similar to our normal upgrade process)
- If you don't want the current server's logs to reside on the new server, delete the files in the Data\Log folder
- Since the copy/paste overwrote the license files on the new server with those for the current server, you need to replace the license files
- Copy xtraction.lic into the Data\Configuration folder
- Copy datamodeleditor.lic into the Tools folder
On the new server, perform the following steps to update the configuration to work on the new server:
- Run the Xtraction Settings utility and update the Xtraction Database connection information if using a new database. Be sure to change any other settings as necessary for the new server.
- If the new Xtraction server will be reporting against different databases (for example, dev/test databases instead of production), use the Data Model Editor to update the connection strings appropriately
- If you did not perform these configuration steps during the Xtraction installation, be sure to check the user accounts used by the Xtraction application pool(s) and Xtraction Task Manager service