If you are upgrading from GPFS , you can choose between the following upgrade options. GPFS Administration and Programming Reference Click below to view this publication ?. File System V documentation, where you can find information about how to install, administer, maintain, and use GPFS
|Published (Last):||8 May 2010|
|PDF File Size:||12.53 Mb|
|ePub File Size:||11.90 Mb|
|Price:||Free* [*Free Regsitration Required]|
At this point, you can use the installation toolkit for installation or deployment of new functions and for future upgrades.
NodeName is the name of the node on which the operating system upgrade will be done. Given the age of GPFS 3. Run the necessary platform-specific commands to upgrade GPFS.
The steps in this procedure are similar to the steps in the online upgrade procedure. For GPFS-only configurations, the process is now complete.
Upgrading from GPFS 3.5
Regardless of which method you are using, if 3.55 want to install and configure CES protocols after upgrading to the latest level, you must create a CES shared root file system of size 4 GB or greater.
Perform any necessary operating system upgrades. For each node in the cluster, do the following steps. At this point all code is at the upgraded level, but the cluster gppfs not upgraded and new functions cannot be configured until the upgrade is completed.
For more information, see Setting up Cluster Export Services shared root file system.
Upgrading from GPFS
Offline upgrade, complete cluster shutdown This scenario is applicable if you can shut down the entire cluster and perform the upgrade. Confirm that the upgraded operating system level is one that is supported by the version of IBM Spectrum Scale to which the system is being upgraded. Re-enable the GPFS autoload setting by issuing the following command. Extract the IBM Spectrum Scale installation image so that all installation files rpm, deb, bff, msi, and so on are available.
After the operating ypfs is upgraded and any required reboots are complete, follow the steps for upgrading GPFS. You can also create this file system from multiple NSDs, each of which are replicated to help with redundancy.
This file system is used for CES protocol state data and it must remain mounted and up on all protocol nodes for the protocols to function. Alternatively, you can perform function additions and upgrades manually. Online upgrade, most functionality remains available Upgrading to the 5. .35 all the nodes in the cluster are upgraded to 4. Unmount GPFS file systems on the node by issuing the following command. At this point, the code is at the upgraded level, but the cluster is not upgraded and new functions cannot be configured until 35.
upgrade is completed.
Operating system upgrades while upgrading from GPFS 3. Upgrading from GPFS 3. Repeat the preceding steps on each node in the cluster one by one after restarting GPFS. For this upgrade path, use the following platform-specific commands instead of those listed in Step 4: However, due to the entire cluster being offline, it is possible to jump straight to the latest code level instead of hopping to an intermediate level, as required during an online upgrade. At this point, all code is at the upgraded level, but the cluster is not upgraded and new functions cannot be configured until the upgrade is completed.