IBM Hub/Switch Switch User Manual


 
Appendix G High Availability
HPSS Installation Guide September 2002 547
Release 4.5, Revision 2
/opt/encinamirror
/usr/lpp/encina
/opt/hpss
/var/hpss
/usr/java130
/usr/local/sammi
Note that this lists default file system mount points only. Determine the appropriate file systems
and mount points for your site before continuing.
The sizing of these filesystems is very important. To determine sizing forHPSS-related filesystems,
see Section 2.10.3: System Memory and Disk Space on page 132. To determine sizing for DCE, Java,
and Sammi file systems, refer to the appropriate documentation for those applications.
It is imperative that these filesystems are mirrored in such a way that each mirrored copy is
stored on a different bus.
G.3.5 Mirror Shared JFS logs
AIX’s JFS (Journaled File System) also requires a logical volume on which to store its log. Each
volume group with at least one JFS will have its own JFS log logical volume. It is important that
these be mirrored across busses as well since JFSs can’t operate without their associated JFS logs.
To create your own JFS logs, instead of using the LVs that AIX creates automatically, do the
following after creating the volume group but before doing anything else:
1. Create a Logical Volume of type jfslog with a size of one logical partition (1 LP), sequential
update policy, and 2 copies of each LP.
2. Format the Logical Volume as a JFS log using the logform command:
% logform /dev/<LVname>
Now any JFS that is added to this volume group will use this JFS log.
G.3.6 Connect Robotic Tape Libraries
Since an HA HPSS system has two nodes which need to be capable of performing all functions of
an HPSS core server, it is important that any connections to robotic libraries be identical on both
nodes. For example, if /dev/lmcp0 is a control point for a library on one node, then /dev/lmcp0 also
needs to be a control point to the same library on the other node. If your library performs security
checking by IP address or hostname, use the IP address and interface name of the service adapter
when adding your HA system to the library’s security list.