HP Matrix Operating Environment Software - Manual (Page 34)

• Creation or deletion of a pset using psrset on a system where gWLM is managing pset
compartments.
• Performing online cell operations using parolrad.
• Enabling and disabling Hyper-Threading.
To make use of these additional resources using the gWLM command-line interface:
1. Undeploy the SRD containing the systems that you want to adjust.
2. Make your adjustments.
3. Re-create and re-deploy the SRD.
4. Ensure policies used in the SRD do not unintentionally limit their associated workloads'
resource requests.
To make use of these additional resources using the gWLM interface in HP SIM, follow the
procedure given for that interface above.
NOTE: After manually adjusting the number of cores in an SRD, always confirm the changes
after two gWLM resource allocation intervals have passed. Changes might not be as expected
due to gWLM behaviors such as the ones described below.
•
In an SRD with nested partitions, gWLM samples the inner partitions for their sizes before
sampling the outer partitions. Adjusting resources between these samplings can cause gWLM
to report incorrect sizes. If you encounter this issue, try making your adjustment again.
• In an SRD with nested partitions that includes vpars, assume you manually add cores from
an unmanaged vpar. If you later remove those cores—without returning them to an
unmanaged vpar before gWLM samples compartment sizes—those cores are deactivated.
Manually adjusting memory resources
The vparmodify command enables you to move memory from one vpar to another. However,
gWLM cannot move CPU resources while a vparmodify operation is in progress. If a memory
move takes longer than gWLM's resource allocation interval, gWLM will not be able to satisfy
CPU resource requests for the missed intervals. gWLM resumes allocating resources once the
memory move is complete.
You might see SIM events indicating vparmodify commands executed by gWLM are failing.
The vparmodify commands fail with the following message:
A conflicting resource migration is in progress on this vPar.
Once the pending migration completes, the gWLM operation should complete.
Setting aside space for historical data
HP recommends that you allocate 4 GB of storage for every 100 workloads you will manage with
gWLM. With a 5-minute sampling interval, this is enough space to store 2 years of data, which
you can then use for capacity planning and performance management.
On HP-UX, the provided HP System Management Database (HPSMDB), also known as
PostgreSQL, stores its data in the /var/opt/ file system. On HP-UX and Windows systems
using Oracle, set aside the space in the file system used by the configured database.
Backing up the VSE Management Software database
NOTE: This section applies only to the provided HP System Management Database (HPSMDB).
The VSE Management Software database contains configuration data as well as historical
performance data. To create a backup of your gWLM database, use the vseinitconfig
--backup
command . To make use of a backup file, use the vseinitconfig --restore
command.
34 Additional configuration and administration tasks