Technical data

Virtual Partitions (vPars) Management on nPartitions
vPar Configuration Data on nPartitions
HP System Partitions Guide: Administration for nPartitions, rev 5.1 463
vPar Configuration Data on nPartitions
This section covers configuration data issues related to using vPars in
nPartitions on HP Superdome servers.
Virtual Partition configuration data by default is stored in the
/stand/vpdb file, although you can specify that another file be used as
the vPars database.
When you have multiple vPars booted (in an “Up” state) on an
nPartition, the vPars databases for all booted vPars are kept coherent;
any changes to vPar configurations are saved in each of the booted
Virtual Partition’s databases.
Virtual Partition configuration data is not stored in the nPartition
complex profile data. As a result, vPar changes do not affect nPartition
configurations.
The following list describes some issues related to managing both
nPartition and vPars configuration data in a Superdome nPartition.
• Boot Paths for Virtual Partitions and nPartitions
Each nPartition’s boot path variables (PRI, HAA, ALT) are stored in
the nPartition’s profile data.
The vPar boot device paths (PRI, ALT) are stored in the vPars
configuration database.
The parmodify and parstatus commands always can report and
modify nPartition boot device path details.
When one or more vPars is booted in an nPartition, the setboot
command affects the current vPar’s boot paths and settings.
When HP-UX is booted in a non-vPars nPartition, the setboot
command and others affect the local nPartition.
• vPar Configuration Data Coherency
Only the vPars configuration database (/stand/vpdb) residing on
each vPar’s currently booted device’s filesystems is updated to reflect
any changes.
Any booted vPar that has multiple boot devices (such as boot and
altboot) can have one current and one outdated copy of vPar data.