H06.27 Software Installation and Upgrade Guide

3 Installation, Migration, and Fallback Considerations
See the Readme file and the appropriate softdocs for the latest information on any migration or
configuration steps. Considerations in this chapter are categorized according to the RVU at which
they were introduced.
H06.03
Kernel-Managed Swap File (KMSF)
Servers running H-series RVUs require more swap space than do NonStop S-series servers. The
default is 512 megabytes for each processor. Depending on your hardware and software
configuration, more swap space might be needed. Using KMSF, monitor the actual virtual memory
consumption. To check the size of the configured swap files for each processor, at a TACL prompt,
start NSKCOM and enter the STATUS SWAPFILE command. For more information on commands
and usage, see the Kernel-Managed Swap Facility (KMSF) Manual.
IOAM and Migrating Existing Data to an Enterprise Storage System (ESS)
G-series application programs that reside on an ESS and are run on a NonStop S-series system
might require migration changes to run on a NonStop NS-series server and H-series RVU. For more
information, refer to the H-Series Application Migration Guide.
The migration of existing data from internal SCSI-attached, 514-byte sector disks to industry
standard, 512-byte sector disk subsystems includes an improved method for checksum protection.
The new checksum protection method employed for unstructured files requires the data stored on
disk be contiguous and aligned in units of 28 kilobytes.
When a nonpartitioned unstructured file is created or migrated to an ESS, the extent sizes are
rounded up to a mod-14 boundary, since an extent page is 2 KB. Rounding ensures continuity of
the data set protected by the checksum. This design ensures the best possible performance for
unstructured files, without adding significant overhead for checksums. Each 28 KB of data is
protected with a 4-KB check block, which contains the checksum information.
Partitioned unstructured files cannot be migrated to an ESS without first performing a migration of
all partitions of the unstructured file set to a mod-14 extent boundary. Partitioned unstructured files
must use the same extent size and maximum extents for all partitions because positioning is
dependent upon a consistent size for each of the partitions. Online migration attempts will abort
when an unstructured partitioned file without mod-14 extent sizes is present on the source disk.
Before migrating to an ESS, rebuild all partitions, using a mod-14 extent size. Perform an offline
copy to a new partition set.
The FCHECK utility (introduced in G06.24) includes a migration option that reports the files that
cannot be migrated to ESS because of this format limitation, in addition to reporting the amount
of disk space required for check block protection.
OSS Database Files
See the Open System Services Management and Operations Guide and the Open System Services
Installation Guide for information about updating and maintaining OSS database files. See the
Interactive Upgrade Guide 2 for new OSS features and for a summary of migration or installation
issues.
H06.03 37