ALM | Requirements Management | Testing | Project Planning | Bug Tracking | Modeling | Version Control | VoIP IP PBX Phone System
Home | Latest Versions | Product Presentations | Download Free Evaluation | Blog | Developers Forum | Delta 1000 Gateway

Fully migration from one server to another

Author Topic: Fully migration from one server to another  (Read 6601 times)

oper557

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
Fully migration from one server to another
« on: December 27, 2006, 07:58:57 AM »
Hello,
We have bought new server (hardware) and now want fully migrate from one server to another. How can we do it?

Our current configuration:
Windows XP SP2
Microsoft SQL Server 2000 Enterprise Edition
Borland StarTeam 2005 R2

Our new server with Windows 2003 SP1

Administrator

  • Administrator
  • Newbie
  • *****
  • Posts: 40
  • Karma: 0
    • View Profile
Re: Fully migration from one server to another
« Reply #1 on: December 27, 2006, 12:57:43 PM »
Overview:


The StarTeam server configuration is comprised of three things:

1. The starteam-server-configs.xml file.

2. The entire repository.

3. A supporting database, Oracle, SQL, or MSDE.


To move a StarTeam 2005 server from one physical system to another follow the process below.


1.  Install StarTeam 2005 on the target system. If you are installing StarTeam 2005 from CD follow process "A". For installations from a download location, process "B".

A. Install the StarTeam 2005 server software on the target system, then download and install server patch 11, available here:

http://ftp://sacust:generic@bekins.borland.com/support/Patches/7.0/2005Server11.zip

B. If you are installing from a download location, download and install the StarTeam 2005 utilities first and then the server software second.

The utilites can be downloaded from here:

http://ftp://sacust:generic@bekins.borland.com/StarTeam2005/2005STUtility.exe

The server software can be downloaded and installed from here:

http://ftp://sacust:generic@bekins.borland.com/StarTeam2005/2005STServer.exe

After installing both the utilities and the server, install server patch 11 from here:

http://ftp://sacust:generic@bekins.borland.com/support/Patches/7.0/2005Server11.zip


2. Copy the entire repository and starteam-server-configs.xml to the target system. If the database is also being moved and will be run on the same physical system copy the database backup to the target system as well.


3. Rename the starteam-server-configs.xml in the new StarTeam 2005 server installation and replace it with the starteam-server-configs.xml from the target system. To verify if this step was followed correctly the name of the server configuration that appeared in the Server Tools on the soruce system should now appear in the Server Tools menu on the target system. To find Server Tools on the same physical system where the StarTeam server is installed click "Start"->"Programs"->"StarTeam"->"StarTeam Server"->This will open a window titled "Server Tools". Edit the starteam-server-configs.xml file in it's new location using notepad so that the line that reads "Repository Path" lines and "LogPath" to reflect their new locations on the target server.


4. Restore the database. This process will vary depending on database type, for SQL server there is a create backup/restore backup process, for Oracle EXP/IMP, and for MSDE the MSDE Admin Tool will need to be used.


5. Within Server Tools on the target system highlight the server configuration and click "Properties". Verify that the log path has been changed to reflect your edit to the starteam-server-configs.xml file. Select the databse tab and use the ODBC database name to create a new ODBC connection. This process will differ again depending on database type, for SQL or MSDE create a system DSN specifying the target database. For Oracle a new ODBC driver will need to be installed as described in Chapter 4 of the StarTeam 2005 Installation Guide: "Using StarTeam with Oracle". Regardless of the database type specified click "Verify" when the process is completed to confirm that the ODBC configuration has been created successfully. Click "OK" to close.


6. From within Server Tools highlgiht the server configuration and verify that the "Execution mode" is set to "Application", if not click "Remove service".


7. Start with overrride - With the StarTeam server configuration still highlighted click "Start with override". There will be fields for the TCP/IP protocol endpoint and attachments path. The default endpoint is 49201, and the attachments folder is stored within the repository.


Note:  If the Starteam server starts successfully verify that client connections allow files to be checked out. If the StarTeam server fails to start there should be an error onscreen and an entry in the server.en-us.log. Any mention of the Event Viewer can be safely disregarded.

Author: J Hartman

oper557

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
Re: Fully migration from one server to another
« Reply #2 on: December 27, 2006, 02:09:34 PM »
Thanks! I can do it!

Fackier

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
    • View Profile
Re: Fully migration from one server to another
« Reply #3 on: June 23, 2009, 02:32:32 PM »
HI Hartman,

Your document is very much helpfull us to migrate our starteam 2005 server to another hardware. However we are trying to configure Starteam 4.2 on the same server. Please let us help us to restore starteam 4.2 on the same server with its recent backup.

Regards,
Fackier