Moving Server Configurations Overview

Overview for Moving a Server Configuration

The following provides a database-independent overview for moving a server configuration:

1. Shut down the server configuration. Because of Native-II vaults, you do not have to do this, but it is still a good idea.
2. Create a database backup.
3. Verify the location of the files that you need to move. These are the database backup, starteam-server-configs.xml file, repository including Native-II archives if not located within the repository.
4. Copy the files from the source to the target location.
5. Copy the entry for the source server configuration into the target starteam-server-configs-xml file. If this file does not exist on the target machine, then you can copy the entire file and delete any entries from the file for server configurations that do not exist on the target machine. If this file does exist on the target machine, then take care to copy only the section needed for the server configuration that you are moving to the target machine.
6. Correct the repository/log path in starteam-server-configs.xml for the specified server configuration.
7. Restore the database from backup.
8. Configure the database connection.
9. If needed, start the server configuration with the Start with Override option.

Incorrect Assumptions about Moving Server Configurations

The following are some incorrect assumptions about moving server configurations that lead to errors, so do not try any of the following methods:

• Just move the database and create a new server configuration pointing to it.
• The server configuration consists only of a database and repository. Note that starteam-server-configs.xml file is also required when you move a server configuration.
• Just use the Migrate Database toolbar button. Note that this option migrates database types only.