If you currently use the INI installation method and wish to convert to using the Staging method, there is currently no easy way to do that. The procedure involves uninstalling fully on each node, then reinstalling from scratch.
If you still wish to convert from the INI installation method to using the Staging method, use the following procedure:
Place cluster(s) in Maintenance Mode:
shell>cctrlcctrl>set policy maintenance
On the staging node, extract the software into
/opt/continuent/software/{extracted_dir}
shell>cd /opt/continuent/softwareshell>tar zxf tungsten-clustering-7.1.4-10.tar.gz
If this is an Composite Active/Active topology using v5 or earlier, make sure you extract both the clustering and replication packages.
Create the text file config.sh
based on the output from tpm reverse:
shell>cd tungsten-clustering-7.1.4-10shell>tpm reverse > config.sh
Review the new config.sh
script to confirm everything is correct, making any needed edits. When
ready, create the new configuration:
shell> sh config.shIf you are using an Composite Active/Active topology using v5 or earlier, repeat these steps using the replicator staging directory. For example:
shell>cd tungsten-replicator-7.1.4-10shell>/opt/replicator/tungsten/tools/tpm reverse > config.shshell>sh config.sh
Review the new configuration:
shell> tools/tpm reverseSee Section 10.3, “tpm Staging Configuration” for more information.
On all nodes, uninstall the Tungsten software:
Executing this step WILL cause an interruption of service.
shell> tpm uninstall --i-am-sureIf you are using an Composite Active/Active topology using v5 or earlier, repeat these steps using the replicator tpm command. For example:
shell> /opt/replicator/tungsten/tools/tpm uninstall --i-am-sure
On all nodes, rename the tungsten.ini file:
shell> mv /etc/tungsten/tungsten.ini /etc/tungsten/tungsten.ini.oldOn the staging node only, change to the extracted directory and execute the tpm install command:
shell>cd /opt/continuent/software/tungsten-clustering-7.1.4-10shell>./tools/tpm install
If you are using an Composite Active/Active topology using v5 or earlier, repeat the install using the replicator staging directory. For example:
shell>cd /opt/continuent/software/tungsten-replicator-7.1.4-10shell>./tools/tpm install
Once all steps have been completed and the cluster(s) are stable, take each cluster out of maintenance mode by setting the policy back to automatic:
shell>cctrlcctrl>set policy automatic