6.3

Table Of Contents
Procedure
1 In vRealize Operations Manager, select Administration > Policies.
The Active Policies tab displays the current policies in eect.
2 Click the Policy Library tab, and click the plus sign to add a custom policy.
3 In the workspace navigation pane, click  Started and dene the basic information for the policy.
a In the Name text box, enter vSphere Production Virtual SQL Servers.
b In the Description text box, enter Analyze capacity of virtual SQL Servers.
c To start with a base policy, select Default Policy from the Start with drop-down menu.
4 View the policy conguration seings.
a In the policy workspace, click Select Base Policies.
b To view the policy conguration for virtual machine objects, click the Show changes for drop-
down menu, click vCenter Adapter - Virtual Machine, and click the Show object type lter.
The Virtual Machine policy conguration appears in the right pane.
c To view the inherited seings, in the Policy Preview pane, click  inherited from base
policy.
5 In the workspace navigation, click Analysis .
6 In the workspace navigation, add the following object types to the list so that you can change their
seings.
a Click the drop-down arrow, click vCenter Adapter - Cluster Compute Resource, and click the
lter.
b Click the drop-down arrow, click vCenter Adapter - Data Center, and click the lter.
c Click the drop-down arrow, click vCenter Adapter - Host System, and click the lter.
d Click the drop-down arrow, click vCenter Adapter - Resource Pool, and click the lter.
e Click the drop-down arrow, click vCenter Adapter - Virtual Machine, and click the lter.
The analysis seings for these object types appear in the right pane.
7 On the Cluster Compute Resource bar, click the double arrows to expand the list of analysis seings.
8 Locate Capacity Remaining Time Remaining and click the lock buon to enable changes.
9 In the resource table, set the overcommit for Memory Allocation value to 0 so that
vRealize Operations Manager does not overcommit these objects for your SQL Server policy.
10 In the resource table, set the overcommit ratio for CPU Allocation to 2 so that
vRealize Operations Manager overcommits a 2:1 ratio for CPU allocation on each SQL Server.
11 Repeat Step 7 through Step 10 for each object type that you added to the right pane.
12 Click Save.
You created a policy and made minor changes to seings so that vRealize Operations Manager can analyze
and report on your SQL Server objects.
What to do next
Congure the alert denitions and symptom denitions for your SQL Server policy. You will apply the
policy to your SQL Server object groups.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 89