If you are upgrading a Server that is part of a cluster, follow the procedures below.
To upgrade in an environment where EFT Server is installed to the local hard drive on each node, so that only the configuration files are on the shared resource:
Download the new version’s installation file to each of the two nodes.
Back up the configuration files directory on the shared resource.
Verify which node is currently the passive node (does not have ownership of the EFT Server service and its resources), and begin with that one.
Run the new installation file on the passive node, selecting Repair when prompted.
When completed, change ownership of the EFT Server service and its resources to the newly upgraded node.
Run the new installation file on what is now the passive node with the older version, selecting Repair when prompted.
Verify that the upgrade was successful:
Log in through the administrative interface and double-check that the settings are as expected, including checking the version shown in Help > About.
Change ownership to the passive node, and then repeat Step A.
Remember to upgrade to the same version any installations of the Administrative Interface on any other systems from which remote administration is performed.
To upgrade in an environment where EFT Server is installed directly to the shared storage (not recommended):
Download the new version’s installation file to each of the two nodes.
Back up the configuration files directory on the shared resource.
Take the EFT Server group offline.
Verify which node is currently the active node (has ownership of the EFT Server service and its resources), and begin with that one.
Run the new installation file on the active node, selecting Repair when prompted.
When completed, change ownership of the EFT Server service and its resources to the previously passive node.
Run the new installation file on what is now the active node, selecting Repair when prompted.
Bring the EFT Server group online.
Verify that the upgrade was successful:
Log in through the administrative interface and double-check that the settings are as expected, including checking the version shown in Help > About.
Change ownership to the passive node, and then repeat Step A.
Remember to upgrade to the same version any installations of the Administrative Interface on any other systems from which remote administration is performed.