4.4.3. Upgrading from Tungsten Clustering 1.5.3/1.5.4 to Tungsten Clustering 5.1
You can upgrade directly from Tungsten Clustering 1.5.3 or Tungsten Clustering 1.5.4
to Tungsten Clustering 5.1 using the standard update procedures.
When upgrading to Tungsten Clustering 5.1 from Tungsten Clustering
1.5.3/1.5.4, changes to the way witness hosts are used and identified mean
that you should modify your configuration before completing the upgrade
The witness changes that affect the upgrade are as follows:
Witnesses must be on the same network subnet as the existing managers.
Dataservices must have at least three managers to provide status check
Active witnesses can be created; these install only the manager on
target hosts to act witnesses to check network connectivity to the
configured dataserver and connectors configured within the service.
If you are upgrading a host which satisfies conditions (1) and/or (2) in the
above list, you can perform an upgrade using tpm update.
If your current witness host is not on the same network segment as the rest
of your dataservice, the witness host must be removed from the
configuration. Alternatively, you can add or update an existing witness host
to be an active host witness within the cluster.
To upgrade a cluster and add the required active witnesses to the cluster,
or to add additional active witnesses to a cluster which already has the
required number of implied witness hosts, the configuration must be upgraded
first before deploying the service.
On your staging server, download the release package.
Unpack the release package:
Change into the directory:
Fetch a copy of the existing configuration information:
Update the configuration with additional witness hosts:
service_name --enable-active-witnesses=true \
Run the update and installation process:
If you have multiple services configured that require active witnesses, you
must update each service with additional witness hosts.