This chapter provides information about the software upgrade strategy.
You can upgrade your software while your day-to-day operations are running. You must, however, expect performance to be degraded while the software is being installed.
| Note: Applying a software update takes approximately one hour. This is in part due to the 30 minute delay which is inserted to allow the multipathing software to recover. |
Software and microcode for the SAN Volume Controller and its attached adapters is tested and released as a single package. The package number is increased each time a new release is made, although only some of the components might have changed. Included in the package are Linux, Apache, and the SAN Volume Controller software.
If you are upgrading through more than one level; for example, from level 1 to level 3, under some circumstances, you might need to install an intermediate level. For example, if you are upgrading from level 1 to level 3, you might need to install level 2 before you install level 3. Details of any prerequisite levels are provided with the source files.
| Attention: Applying a software upgrade while the node is in service mode results in deleting the node from the cluster. Status information stored within the node will be deleted, and this causes data loss if the cluster is dependent solely on this node. |
When upgrading cluster software where the cluster participates in one or more inter-cluster relationships only one cluster should be upgraded at a time. That is, both clusters should not be upgraded concurrently. The software upgrade should be allowed to complete one cluster before it is started on the other cluster. If both clusters are upgraded concurrently, it may lead to a loss of synchronization. It may further lead to a loss of availability.
| Attention: Ensure that you have no unfixed errors in the log, and that the Cluster Time/Date is correctly set. |