|
Last modified: 27 Dec 2007
As a rule, H-Sphere web or mail servers with NetApp load balancing
are configured in such a way that H-Sphere regards master and slave servers as one server
and "sees" only master servers.
Therefore, the H-Sphere upgrade script installs new software only to master servers
and does not automatically upgrade slave servers.
The following procedure allows updating H-Sphere on the NetApp slave servers as well:
Create H-Sphere physical servers for each Web/mail slave servers, if no exists. Add H-Sphere logical servers to each physical server created there, if no exists. Make sure it is always turned off for signup. Perform the standard
H-Sphere update. Check the latest update log (located in the /hsphere/update directory on the CP server)
to ensure the software is correctly updated on the slave servers.
For example, when updating to HS 2.4.2 Beta3:
cd /hsphere/update
vi U24.2b3.log.200412210900
On the master and slave servers, do steps 6.2 and 6.3 of the
NetApp Configuration document
to return to the correct Apache configuration for NetApp.
|
