3.Convert Configuration Metadata; 4.Convert Subsystem Metadata - IBM High Performance Storage System HPSS Installation Manual

High performance storage system
Hide thumbs Also See for High Performance Storage System HPSS:
Table of Contents

Advertisement

The first program used in the 4.5 conversion is the information collection utility,
db_convert_collect_info. This utility will gather configuration related information based on input
provided about the 4.5 HPSS system. The program will save the information to several text files
located in the /var/hpss/convert/6.2 directory. This utility must be run once for each subsystem and
must be run prior to invoking any other conversion utilities.
All configuration metadata will be placed in the global configuration database designated when
running the db_convert_collect_info utility. Subsystem metadata should be placed in its own
separate database. When prompted by the db_convert_collect_info utility for a subsystem database
name, ensure a unique database name is provided for each subsystem.
6.3.13.3. Convert Configuration Metadata
Run the db_config_convert script. Perform this step on the root subsystem only.
% db_config_convert
This script calls a series of programs that will perform all of the HPSS 4.5 configuration metadata
conversions. This script provides a good way of performing a practice conversion. The program runs
in a matter of minutes depending on the complexity of the the 4.5 HPSS system (i.e. the number of
subsystems and the total number of servers), and can run against a fully active 4.5 HPSS system.
Prior to running this script, execute the db_convert_collect_info script and ensure both SFS and DB2
are running. This script only needs to run once on the root subsystem node. To run the script, login
as root and provide the complete and correct SFS global configuration file CDS pathname as a
command line argument. For example,
% su – root
% db_config_convert
This script has no restart capability, but because it is short running and it performs read-only
operations on the 4.5 metadata, it can be rerun again if desired or if it encounters an error. When
running this script a second time and if you want to delete the previously converted metadata, answer
'Y' when prompted to empty the related DB2 tables that were populated during the previous run;
otherwise, the script will terminate due to an error (-2014) related to duplicate DB2 entries. The
script places all configuration metadata into the global "cfg" database.
To determine whether the program completed successfully, search the output file for keywords such
as "Error:" and "Warning:". See Section 6.2.7: Capturing the Metadata Conversion Output on page
185 and Section 6.4: Metadata Conversion Troubleshooting Procedures on page 227.
6.3.13.4. Convert Subsystem Metadata
Run the db_subsys_convert script.
% db_subsys_convert /.:/encina/sfs/hpss/globalconfig <subsys id>
[readonly]
The db_subsys_convert script invokes a series of programs that will convert all of the subsystem
related metadata. The script completes execution in less than an hour depending on the complexity
or size of your HPSS system (i.e. the number of subsystems and the total number of servers) and can
run against a fully active 4.5 HPSS system.
Prior to running this script, execute the db_convert_collect_info script and ensure both SFS and DB2
are running. This script must be run once for each subsystem. To run the script, first login as root.
Next, provide the complete and correct SFS global configuration file CDS pathname and the
HPSS Installation Guide
Release 6.2 (Revision 2.0)
/.:/encina/sfs/hpss/globalconfig
/.:/encina/sfs/hpss/globalconfig
July 2008
204

Advertisement

Table of Contents
loading

This manual is also suitable for:

Hpss 6.2

Table of Contents