Air Cleaner User Manual

ManualsBrandsIBM ManualsAir CleanerIBM Tivoli Storage Manager Version5Release6

181

182

183

184

185

186

187

188

189

190

Chapter 14. RS/6000 Scalable POWERParallel Systems

(SP)

Boot and Install Utilities

The RS/600

systems, unlike the non-SP RS/6000 systems, have special

requirements for installing and cloning. The RS/6000 SP System is comprised of a

Control Workstation (CWS) and one or more nodes. Each node and the CWS are

independent machines that work together using a complex system of network

daemons, configuration files, and hardware. The nodes do not have floppy drives

or LED panels consistent with non-SP RS/6000 systems.

SysBack backup and restore operations on the SP are identical to non-SP RS/6000

systems. When these operations are performed across network interfaces, not to

locally attached tape devices, the setup and configuration requirements do not

differ from the non-SP systems. However, the installation process requires some

additional considerations.

This chapter provides the information necessary to fully exploit SysBack

installations in an SP environment.

Advantages of the SysBack SP Boot and Installation Utilities

In previous versions of SysBack, the SP administrator had to perform several

specific SP installation activities manually. For example, if a node was reinstalled,

the administrator had to set the node to “disk” in the SDR to enable SysBack to

complete the installation process rather than PSSP. The node would have to be

manually customized and the PSSP script run. If the node was cloned from the

image of another node, further actions were required, including updating the

/etc/niminfo file and other configuration files.

In SysBack Version 5, the product works with PSSP to handle these SP system

specific issue during the node’s installation process. SysBack sets the SDR’s

bootp_response,runsetup_server, perform node conditioning, and runs the PSSP

script. Reinstallation of a node using the SysBack SP boot and installation utilities

results in a fully recovered node.

The administrator continues to perform the usual activities associated with

preparing an SP node to be installed, as well as, the post-installation application

and network specific activities.

SysBack expects to use the same NIM SPOT and LPPLOURCE that is used when

the node is installed with a mksysb image using the default SP installation process.

An indication that the node has been properly prepared for installation is that the

node can be successfully installed with the SP/NIM designated mksysb image

using the standard PSSP installation process.

For more information on how to work with a nodes NIM SPOT and LPPSOURCE,

see the publications:

v PSSP Command and Technical Reference, Volume 2

v PSSP Administration Guide