How to Move or Copy a 5.x StarTeam Repository or Its Parts.



How to Move or Copy a 5.x StarTeam Repository or Its Parts.


Information in this Brief applies to:

  • StarTeam 5.x Server
  • Windows


Sometimes it may be important to move or copy a StarTeam Repository or its parts to a new Physical Server machine. To successfully achieve this goal you will need to copy all the essential StarTeam Repository and Database files to the target destination recreating the same configuration on a new machine. It is recommended that the Repository be copied as opposed to moved, to minimize the down time and assure that the target destination is fully functional before deleting the original repository files.

Please carefully test your modified repository configuration before disabling or deleting the old repository and configuration.

The steps for moving a 5.1 or 5.2 repository are slightly different than moving 3.x and 4.x repositories.


It is best, to move all of the repository to the same relative location. For example, on a Windows platform, you would want to copy the entire repository from its old location C:\Starteam_Repository on the original server machine to the new Starteam server at the same relative location C:\Starteam_Repository. The StarTeam Repository is the startup path location for the Starbase Server configuration, it is where the Server.Log will be created and all of the Vault Archive Files, Attachments and Vault Cache files are kept. If you are using an Access Database, this is where the database file is kept also.

1. Before you move a Repository, make certain all the appropriate Repository items are backed up. The backed up Access **Database and Vault files should all be backed up at the same time. It is important that this back up occurs while StarTeam is either locked or better yet, not running so no one is using the Starbase server.

**Note. If you are using a MS SQL, Oracle or DB2 database, make sure that you are backing up the database at the same time you are copying the Repository, it is imperative that these two separate parts remain in completely synchronized.

2. Verify and note the Repository path and the relative location of all the folders and child folders. Once you change this information in StarTeam it may be difficult to locate the files and folders you need to move.

To verify the startup path and folder locations:

a. Display the Server Administration dialog by doing one of the following:

i. From the StarTeam Client, select Tools\Server Administration from the menu bar.
ii. On the computer where Starbase Server is installed, start Server Administration Tool.

b. From the Server Administration dialog?s left pane, select the server configuration you anticipate moving.
c. Click the Configure Server button. The Starbase Server Configuration dialog opens.
d. Make a note of the path information in the following text boxes:

i. General Tab: Server Startup Log Path and Attachments Path
ii. Vault tab: Vault Path, Disk Cache Path, and Archive Path

e. At this time it is important to also make a note of the information from the Database tab: Database server/DSN

3. Make certain that Starbase server is installed on the target system. Ensure the Starbase server is not running.

4. Copy all the desired files and folders to the target destinations. These files/folders etc. may include:

a. StarbaseServer.ini (by default located in the installation folder of Starbase Server). You will need this file moved to the different server computer at the same time as the copy of the Repository.
b. The StarTeam Vault folder and all its folder/file contents (Archive and Cache folders and contents)
c. The StarTeam Attachments folder and all its file contents
d. The StarTeam Database folder and all its file contents. If you are using MS SQL, Oracle or DB2, you will need to make sure that the Database Server is running.

5. Verify or recreate the ODBC connection on the target system:

a. From the Windows Start button go to Settings and navigate to the Control Panel and to the Data Sources ODBC.
b. In the ODBC controls, select the System DSN tab.
c. Is your DSN (noted in 2e. above) listed?
d. If no, click on the Add button.

i. Select the appropriate database driver from the list.
ii. Click on Finish
iii. Enter the Data Source Name (noted in 2e. above).

e. Click on Select and locate the moved target database in the repository Database folder.

Note: If you are using either MS SQL, DB2 or Oracle you will need to follow the appropriate steps to reestablish connectivity that is appropriate for that system according to the StarTeam Administrators Guide.

6. At this time, because you have copied the StarbaseServer.ini from the original Server Machine, the configuration will show up in Server Tools as it did on the original machine. Select the Configuration for which you have relocated. This is a very important, you do not need to create a new configuration, please do not attempt to create a new configuration of the same name, if it does not appear in the list of configurations, please re-copy the StarbaseServer.ini to the new machine.

Take these steps before starting StarTeam.

a. Click on the Configuration Properties button.
b. With the General tab selected, click on the Verify. You generally need to know the Cipher Phrase to successfully complete this step.

Contact StarTeam Support if you do not know your Cipher Phrase. Just create a web case and attach the StarbaseServer.ini file with a request for Borland to decrypt the Cipher Phrase from the file attached.

c. After a successful verification of the Cipher Phrase, select the Database tab and click on the Verify Connection. If you have problems with this check your connectivity with the Database either through the ODBC/DSN or if using Oracle, via Oracle client tools. If you still have problems contact StarTeam Support at (714) 445-4460.
e. You can now start the Starbase Server.

7. If you have moved one or more of the repository folders to different relative locations you will need to redefine those locations before the server is started.

a. From Server Tools, click on the "Start with Override..." button.
b. Browse to or type the new path information for the repository items.
c. Click on OK.
d. Test to make certain that your move is totally successful. Consider adding a test file to a project and check the archive directory for a new file entry matching the appropriate date/timestamp.

While it is usual to move the entire repository, you can move individual parts:

The Attachments Path. StarTeam allows you to attach files to change requests, tasks, or topics. These files are stored in a separate folder on the server. By default this folder is the Attachments folder and is a child of the folder specified for the repository. It has three child folders whose names should not be changed: Changes_Attachments (for change requests), StTasks_Attachments (for tasks), and Topics_Attachments (for topics). If you move this folder, you must also move the currently attached files to that new location. Do so while the server configuration is shut down.

The Vault Path. By default this folder is the Vault folder and is a child of the folder specified for the repository. The Vault folder initially has two child folders: one for the disk cache and the other for the archive. Changing the Vault path does not change the path to either the disk cache or the archive. You do not have to move the Cache and Archive folders unless you change their paths, too.

The Disk Cache Path. The disk cache folder contains copies of the most recently checked-out file revisions. If a user checks out a revision that is already in the cache, the file is copied from the cache rather than from the archive. This speeds up the check out process. The maximum cache size determines how many files can be stored. By default this folder is the Cache folder and is a child of the folder specified for the vault. If you move this folder, you can (but you don?t have to) move the cached files to the new location. If you move these files, do so while the Starbase Server is down. You may want to resize the cache and reset its refresh interval at this time as well.

The Archive Path. The archive folder stores file revisions. By default this folder is the Archive folder and is a child of the folder specified for the vault. If you move this folder, you must also move the archived files to that new location. Do so while the server configuration is shut down.

If you change any of these folder locations, you must restart the server configuration. If you move the entire repository, you usually change all of these folder locations and the startup location.

Old KB# 28383
Comment List