HP UX 11i Workload Management (gWLM/WLM) Software manual Setting database recovery model

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 --backupcommand . To make use of a backup file, use the vseinitconfig --restorecommand.

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

Page 34 Page 36
Image 35
Page 34 Page 36
Contents HP Global Workload Manager 7.4 User Guide Acknowledgements Contents Support and other resources Additional configuration and administration tasksIndex GWLM Overview Benefits of using gWLMComparison of PRM, WLM, and gWLM features OverviewScheduler fss group. gWLM manages a workload by Concepts and terms for using gWLMWould make for a workload-without actually affecting SRD GWLM management modelHow gWLM allocates CPU resources Assumptions Available interfacesFinding more gWLM information Where to find additional informationLearn about other gWLM commands Policy types Configuring gWLM to manage workloadsPolicy types Choosing a policy type Choosing a policy typeCombining the different policy types Using the wizardSeeing how gWLM will perform without affecting the system Getting started with gWLM# /opt/gwlm/bin/gwlmagent Seeing gWLM in action# perl -e ’print $$\nwhile 1 ’ & 1 Fixing the amount of CPU resources a workload gets Common uses for gWLMSetting up gWLM initial setup steps Common configuration tasksCreating a new policy Changing from advisory mode to managed modeChanging which policy is associated with a workload Editing a policyStop managing a workload Adding a new compartment or GiCAP group member to an SRDStop managing an SRD Quick Link Option High-Level view Viewing gWLM reports in monitor-Only modeMonitoring workloads and gWLM Monitoring workloadsMessage logs Monitoring gWLM from the command lineHP-UX /var/opt/gwlm/gwlmcommand.log.0 Monitoring gWLM with GlancePlus Viewing HP Systems Insight Manager eventsSecuring database communications SecurityGeneral security topics Securing gWLM communicationsSecurity Manually adjusting CPU resources Additional configuration and administration tasksSetting aside space for historical data Manually adjusting memory resourcesTips for backup and restore Setting cache size for historical configuration dataSetting database recovery model Creating a database maintenance planCMS properties Setting gWLM propertiesSetting gWLM properties Agent properties # Severe # Warning # Info # Config # Fine # Finer # Finest Communications ports Controlling gWLM’s startup behavior# /opt/gwlm/bin/gwlmagent --enablestartonboot Related events How the automatic restart worksNode Failed to Rejoin SRD on Start-up event Manually clearing an SRD# gwlm undeploy --srd=SRD--force Nested partitions Nesting partitionsChanging the interval in HP System Insight Manager Using gWLM with Hyper-ThreadingChanging the interval on the command line Changing the gWLM resource allocation intervalShows a possible scenario Using gWLM with hosts on multiple LANsMultiple network interface cards Creating Golden ImagesGet the IP address configured for the host using nslookup Incorrectly configured host name or IP addressEnabling or disabling dumping core for gWLM Unable to create new native threadCore dump file is available in root directory Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesTypographic conventions HP authorized resellersRelated information User input Documentation feedback Compatibility with agents Limitations Global Workload Manager known issuesCompatibility with PRM and WLM Unable to build a single shared resource domainHost name aliases are not supported Making a configuration change to a large SRD is slowRare incompatibility with virtual partitions Integrity VM prevents discovery of psets and fss groups Deleting workloads takes a long timeCustom metrics lost on redeploy Information error during shutdownProcess placement using psrset is ignored Major issues Remove old configuration data from the gWLM database Documentation or minor issuesCMS is slow to respond Cell-local processors and iCAP environmentModifying Java while gWLM is running Error during discovery of compartmentsCombining psets and virtual partitions Only one SRD is allowed to be deployed Missing or unexpected historical data system clocks differSample missing at start or end of gwlmreport output Scripts not placed in correct workloads Processes moved to default pset or default fss groupSRD deployment times out and displays a blank screen Application hangs in fss groupUnable to remove workload from nested partitions SRD Configuration of agent and CMS not synchronizedChanges in sizes in Discovery Negative current size for Nonvm Missing historical data gWLM CMS daemon/service restartedUnmanaging a VM or vPar that is on leaves SRD undeployed SRD IndexIndex

UX 11i Workload Management (gWLM/WLM) Software specifications

HP-UX 11i Workload Management (gWLM/WLM) software is an integral component of HP's premier UNIX operating system, designed to enhance system performance and resource management across diverse workloads. This advanced tool allows system administrators to monitor, control, and allocate resources effectively to achieve optimal performance, reliability, and service levels in enterprise environments.

One of the main features of gWLM/WLM is its ability to classify workloads and manage them according to specific policies set by the administrator. By using service level objectives (SLOs), administrators can define the performance criteria for various applications and workloads. gWLM continuously tracks these workloads, ensuring that they adhere to the defined SLOs, thus maintaining a high level of application performance.

The software employs resource pools, which segment resources such as CPU, memory, and I/O bandwidth among different workloads based on predefined priorities. This capability ensures that critical applications receive the resources they require, even during peak usage periods, thereby preventing resource starvation that could lead to system slowdowns or crashes.

Another significant characteristic of gWLM/WLM is its real-time monitoring and reporting capabilities. The software provides detailed insights into resource utilization, workload performance, and system health. Administrators can access this information through a user-friendly interface, allowing for informed decision-making and proactive management.

Integration with HP Serviceguard adds another layer of functionality, enabling high availability for critical applications. gWLM can orchestrate workload migration to ensure that service levels are maintained, even in the event of hardware failures or resource contention.

The technology behind gWLM/WLM is built on advanced algorithms that leverage historical data and predictive modeling to optimize resource allocation dynamically. This means that as workloads change, the system can automatically adjust resource distribution to meet performance targets without the need for constant manual intervention.

gWLM also supports integration with various enterprise management tools, enabling administrators to implement comprehensive monitoring and management strategies across the IT infrastructure. The scalability of gWLM allows organizations of all sizes to benefit from its robust workload management features, ensuring that they can adapt to changing demands in their operational environments.

In summary, HP-UX 11i Workload Management software offers a sophisticated solution for optimizing resource utilization, managing workloads effectively, and maintaining high performance in complex enterprise environments. Its comprehensive features and technologies make it an essential tool for any organization seeking to enhance their IT operations.
Top Page Image Contents