Справочник Пользователя для IBM Flex System V7000 Expansion Enclosure 4939H29

Chapter 13. Maintenance and Troubleshooting 

Draft Document for Review January 29, 2013 12:52 pm

To generate a configuration backup using the CLI, go to: 

Table 13-11 describes the three files that are created by the backup process.

The system upgrade process involves the upgrading of your entire Flex System V7000 
Storage Node environment. The amount of time can vary depending on the amount of 
preparation work required and the size of the environment. Generally allow slightly over 1 
hour for an upgrade.

Before you upgrade, become familiar with the prerequisites and tasks involved. Decide 
whether you want to upgrade automatically or upgrade manually. During an automatic 
upgrade procedure, the clustered system upgrades each of the nodes systematically. The 
automatic method is the preferred procedure for upgrading software on nodes. However, you 
can also upgrade each node manually. 

During the automatic upgrade process, each node in a system is upgraded one at a time, and 
the new code is staged on the nodes. While each node restarts, there might be some 
degradation in the maximum I/O rate that can be sustained by the system. After all the nodes 

svc.config.backup.xml

This file contains your cluster configuration data.

svc.config.backup.sh

This file contains the names of the commands that were issued to 
create the backup of the cluster.

svc.config.backup.log

This file contains details about the backup, including any error 
information that might have been reported.

Attention: 

��

If you experience failover issues with multipathing driver support, resolve these issues 
before you start normal operations. 

��

Ensure that you have no unfixed errors in the log and that the system date and time are 
correctly set. Start the fix procedures, and ensure that you fix any outstanding errors 
before you attempt to concurrently upgrade the code.

��

If you want to upgrade without host I/O, shut down all hosts before you start the 
upgrade. 

��

Some code levels support upgrades only from specific previous levels, or the code can 
be installed only on certain hardware types. If you upgrade to more than one level 
above your current level, you might be required 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 can install level 3. For information about the prerequisites for each code 
level, see the IBM Support website.