Upgrade and Migration Guide

This chapter describes how to perform the following supported upgrade procedures:

Upgrading a 2.0.X, 2.1.X, or 2.5.X tc Server Installation to 2.6

This section describes how to upgrade an existing 2.0.X, 2.1.X, or 2.5.X tc Server installation to tc Server 2.6.X. The upgrade procedure includes the following tasks:

Upgrade Hyperic Server to Hyperic 4.6

If you are using an older version of Hyperic Hyperic Server, Hyperic 4.6 Server includes new features and support for new releases of supported resources. To take advantage of these improvements in Hyperic 4.6, upgrade Hyperic Server on the computer where it is installed. The Hyperic 4.6 setup has an upgrade mode that updates an existing Hyperic Server installation. For complete instructions, see "Upgrade Hyperic Components/Server Upgrade Procedure" in vFabric Hyperic Installation Guide.

Install Hyperic Agent 4.6

After you have upgraded Hyperic Server to Hyperic 4.6, you can use the Hyperic user interface to upgrade Hyperic Agents on computers with tc Runtime instances. Follow the instructions to upgrade Hyperic components in "Upgrade Hyperic Components/Agent Upgrade Procedure" in vFabric Hyperic Installation Guide.

Install tc Server 2.6

Install tc Server 2.6 in a new installation directory and create any new tc Runtime instances you want. Follow the instructions at Installing tc Server to perform the installation. To avoid overwriting files, be sure to install tc Server 2.6 in a different directory than your current installation. For example, if you have installed tc Server 2.1 in the directory /opt/vmware/springsource-tc-server-2.1, you can install vFabric tc Server 2.6 in the directory /opt/vmware/vfabric-tc-server-2.6.

Upgrade Existing tc Runtime Instances to 2.6

Use the tcruntime-instance.sh|bat upgrade command to upgrade your tc Server 2.0 or 2.1 runtime instances to tc Server 2.6. The upgrade command, new in tc Server 2.6, migrates configuration information and applications from an existing instance to a new 2.6 instance.

By default, the upgrade command creates a new instance that uses the same version of tc Runtime as the current instance. If you want to keep the same tc Runtime version, you must ensure that the corresponding tc Runtime release exists in your tc Server 2.6 installation directory. Otherwise, the upgrade command will display an error message and quit. If necessary, copy the tc Runtime release directory from the previous tc Server installation directory into the tc Server 2.6 installation directory.

The script creates the upgraded instances in your tc Server 2.6 installation directory. For example, to upgrade the tc Server 2.1 instance at /opt/vmware/springsource-tc-server-2.1/myInstance, enter the following command in your tc Server 2.6 directory:

prompt$ ./tcruntime-instance.sh upgrade ../springsource-tc-server-2.1/myInstance 

This command creates an upgraded instance with the same name as the original (myInstance) using the same version of tc Runtime.

To change the name of the upgraded instance, include the -i instanceDir option on the command.

To specify a different tc Runtime version, include the -v version option. When upgrading an unpinned instance, you must specify this option. The following example specifies a new instance name and pins the instance to tc Runtime release 7.0.6.A.RELEASE.

prompt$ ./tcruntime-instance.sh upgrade -i myNewInstance -v 7.0.6.A.RELEASE ../springsource-tc-server-2.1/myInstance 

See tcruntime-instance.sh Reference for more information about using this command.