You must continuously monitor the capacity levels of your virtual SQL Server machines, and have vRealize Operations Manager notify you about any degradation in the performance of these objects. You want vRealize Operations Manager to notify you 60 days before these objects begin to experience problems with their capacity levels.
Your VP of Infrastructure has defined a default operational policy and a main production policy for all of the objects in your production environment, and your IT Director has applied these policies to your production environments. Although the main production policy handles the operational monitoring needs for most of your objects, your manager requires that you be notified about any degradation in the performance of your production virtual SQL Server machines. You have vRealize Operations Manager continuously monitor the capacity levels of your virtual SQL Servers so that you can address problems that occur. You have vRealize Operations Manager notify you 60 days before your virtual SQL Servers begin to experience problems with their capacity levels.
Your IT department divided objects into dedicated groups that support the Development, Test, and Production areas. You must use vRealize Operations Manager to continually track and assess the health and risk of the objects in each of these areas.
In this scenario, you create an operational management policy to analyze, monitor, and troubleshoot your objects. You then monitor the results in custom dashboards.
You must first determine the vSphere operational requirements so that you can understand the analysis settings required for your policy. You can then create a policy to monitor your virtual SQL Server objects, and configure the custom policy to include minor differences in the settings for the main production policy.
When you create the custom policy to analyze and monitor your virtual SQL Servers, you configure the analysis settings so that vRealize Operations Manager analyzes specific objects and report the results in the dashboards. You then apply the policy to groups of virtual SQL Server objects.
Verify that the following conditions are met:
You understand the context of this scenario. See User Scenario: Create a Custom Operational Policy for a vSphere Production Environment.
A default policy and a main production policy are in effect for all of the objects in your vSphere production environment.
- Determine the operational requirements for your vSphere production environment.
In this scenario, the following requirements will be applied to the environment.
- Develop a plan to create a custom operational policy that meets the requirements to analyze and monitor the objects in your environment.
- Ensure that virtual SQL Servers continuously have adequate memory and CPU capacity.
- Ensure that you do not overcommit memory on your production virtual SQL Servers.
- Overcommit only a small percentage of the CPUs on your SQL Servers.
In this scenario, you set the value to 2. In some production environments, a typical value might be 4.
- Ensure that vRealize Operations Manager alerts you if the capacity of your virtual SQL Servers drops below the defined thresholds.
- Set the Co-Stop value on your production virtual SQL Servers to an acceptable level so that the SQL Servers do not experience delay because of CPU scheduling contention.
- Determine whether to overcommit compute resources for certain ratios.
After you plan the custom policy requirements, you can implement the policy.
What to do next
Create an operational policy for your virtual SQL Server instances.