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
|Country:||Republic of Macedonia|
|Published (Last):||12 July 2014|
|PDF File Size:||15.72 Mb|
|ePub File Size:||11.17 Mb|
|Price:||Free* [*Free Regsitration Required]|
Run the necessary platform-specific commands to upgrade GPFS.
Upgrading from GPFS 3.5
Alternatively, you can perform function additions and upgrades manually. Online upgrade, most functionality remains available Upgrading to the 5.
For more information, see Setting up Cluster Export Gfs shared root file system. You can also create this file system from multiple NSDs, each of which are replicated to help with redundancy. After all the nodes in the cluster are upgraded to 4. For each node in the cluster, do the following steps.
For GPFS-only configurations, the process is now complete. 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.
At this point, you can use the installation toolkit for installation or deployment of new functions and for future upgrades. Upgrading from GPFS 3. Extract the IBM Spectrum Scale installation image so that all installation files rpm, deb, bff, msi, and so on are available. Unmount GPFS file systems on the node by issuing the following command.
IBM Support: Fix Central – Please wait, Select fixes
At this point, the code is at the upgraded level, but the cluster is not upgraded and new functions cannot be configured until the upgrade is gpsf.
This file system is used for CES protocol state data and it must remain mounted and up on all protocol nodes for the protocols vpfs function. Regardless of which method you are using, if you 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. For this gprs path, use the following platform-specific commands instead of those listed in Step 4: After the operating system is upgraded and any required reboots are complete, follow the steps for upgrading GPFS.
Given the age of GPFS 3.
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. The steps in this procedure are similar to the steps in the online upgrade procedure.
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.
Perform any necessary operating system upgrades. Operating system upgrades while upgrading from GPFS 3. 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.
Repeat the preceding steps on each node in the cluster one by one after restarting GPFS. NodeName is the name of the node on which the operating system upgrade will be done.