G06.28 Software Installation and Upgrade Guide

Resuming Normal Operations
G06.28 Software Installation and Upgrade Guide—541688-001
12-15
Configure SMF (Optional)
As of G06.23, OSS EasySetup no longer requires the process $NULL and the
installation of SPI template files. The product NULL (T6025) is still included on each
SUT.
Configure SMF (Optional)
If you plan to configure SMF, an optional product, note:
•
Migration of data from direct volumes to SMF logical volumes is documented in the
Storage Management Foundation User's Guide.
•
Performance-critical applications that optimize the physical location of their data
might need to specify the PHYSVOL option when creating data files, instead of
relying on the SMF file-placement algorithm.
•
NonStop SQL/MP 3.x must be up and running before you start SMF.
To ensure system configuration integrity, always:
1. Save the system configuration after SMF configuration changes are made.
2. Reload the system from the current system configuration file or the latest version
with SMF changes.
If remote access to files supported by SMF is needed, the remote system must be
running one of these RVUs:
•
Any G-series RVU
•
D43.02 or later D4n.nn D-series RVUs
•
D35.00, plus an additional set of D3n.nn SPRs, including:
°
T9055ACR
°
T9194ABQ
°
T9196ACE
°
T9197ABO
See the T8472ACK or later softdoc for interoperability considerations, including
information on SMF configuration.
Configure the Remote Database Facility (RDF)
The AUDITTRAILBUFFER parameter is a modifier to DP2, which improves the
performance of RDF. Check that an appropriate value is specified for the
AUDITTRAILBUFFER modifier for the master audit-trail disk process. The
AUDITTRAILBUFFER parameter enables you to specify how many megabytes of
buffer space to allocate for the audit-trail buffers. For information on configuring the
buffer size, see the SCF Reference Manual for the Storage Subsystem.
Caution. To maintain data integrity, do not place:
•
SWAP files on a virtual disk process (VDP)
•
TMF audit data on a VDP
•
DSM/SCM files on a VDP