HP Matrix Operating Environment Software - Manual (Page 35)

Setting cache size for historical configuration data
The gWLM CMS daemon or service (gwlmcmsd) maintains a cache of historical configuration
data of workloads. If there are huge number of workloads on the CMS, to avoid the gwlmcmsd
running out of heap space, reduce the size of the cache by setting the
com.hp.gwlm.cms.cachesize
property to a lower value. The com.hp.gwlm.cms.cachesize
is part of the gwlmcms.properties file. The gwlmcms.properties file is located at /etc/
opt/gwlm/conf/
on HP-UX and in C:\Program Files\HP\Virtual Server
Environment\conf\ on Windows. (The given Windows path is the default; however, a different
path might have been selected at installation.)
The default value of com.hp.gwlm.cms.cachesize property is 100.
Backing up the HP Matrix Operating Environment database
NOTE: This section applies only to the provided HP System Management Database (HPSMDB).
The HP Matrix Operating Environment 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.
For more information, see vseinitconfig(1M).
Tips for backup and restore
Here are tips to make the best use of backup and restore:
•
To ensure the latest gWLM data is backed up, issue the following command before using the
--backup
option:
gwlm history --flush
•
If the CMS or the managed nodes have been modified (such as changes in number of cores
or hostnames) between a backup and a restore or you are trying to do a restore on a different
CMS, gWLM will probably not function as expected after the restore.
Setting database recovery model
When the gWLM database is created in Microsoft SQL, the recovery model is set to SIMPLE.
Depending on the needs you can alter the recovery model after the creation of the database using
Transact-SQL statements. The SIMPLE Recovery model requires less space and is easier to manage
than the Full Recovery model, but at the cost of higher data loss risk if any database file is damaged.
Please consult the database vendor's guidelines before choosing a recovery model.
Creating a database maintenance plan
The gWLM database index size can grow if there are huge number of workloads on the CMS. To
reduce the database size to avoid disk space issues, HP recommends that you run a nightly
maintenance plan to rebuild the index.
To create the maintenance plan for Windows CMS using SQL Server:
In SQL Server Management Studio, use Maintenance Plan Wizard to create a Rebuild Index Task.
Specify the database as gwlm and the table as dbo.gwlm_config_wkld with the Reorganize
pages with the default amount of free space
option selected.
Setting cache size for historical configuration data 35