VMWARE VREALIZE OPERATIONS MANAGEMENT PACK FOR. Microsoft SQL Server. Installation & Configuration Guide

Transcription

1 VMWARE VREALIZE OPERATIONS MANAGEMENT PACK FOR Microsoft SQL Server Installation & Configuration Guide

2 TABLE OF CONTENTS 1. Purpose Installation and Configuration Requirements Setting MS SQL User Privileges Licensing Requirements Upgrading the Management Pack Deleting existing dashboards within vrealize Operations Deleting existing adapter instance(s) and objects Installing the Management Pack Uploading the Installation File Adding a License Key Configuring the Management Pack Creating an Adapter Instance and Credential Manually Discovering Resources Configure the Properties File Validate Data Collection Appendix I: Management Pack Folders and Files Appendix II: Revision Notes...16 NOTE: This document supports the version of each product listed, as well as all subsequent versions, until a new edition replaces it. You can find the most up-to-date technical documentation on the Blue Medora support site at: The Blue Medora website also provides the latest product updates. If you have comments about this documentation, submit your feedback to: support@bluemedora.com. 2 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

3 1. Purpose The Blue Medora VMware vrealize Operations (vrops) Management Pack for Microsoft SQL Server Installation and Configuration Guide describes how to install and configure Blue Medora s Management Pack for Microsoft SQL Server for use within vrealize Operations. 2. Installation and Configuration Requirements Before installing and configuring the Management Pack for Microsoft SQL Server, ensure your system meets the following requirements. Table 1: Management Pack Installation & Configuration Requirements VREALIZE OPERATIONS (VROPS) REQUIREMENTS MICROSOFT SQL REQUIREMENTS VERSION(S) vrealize Operations v6.2+ (Enterprise edition only) Microsoft (MS) SQL Server 2008 R CREDENTIALS N/A MS SQL User Name/Password NOTE: Refer to section 2.1 Setting MS SQL User Privileges for information about creating the least amount of permissions for a MS SQL monitoring user. CONNECTION vrops hostname or IP address Hostname or IP address of MS SQL Server Default Instance Port: 1433 NOTE: The Management Pack supports IPv4 and IPv6. NOTE: Certain features and metrics are only available in Microsoft SQL Server 2008 R2 SP1 and Microsoft SQL Server 2012 and above. Additionally, in order to provide the SQL CPU Usage metric on the MS SQL Server resource, a default instance must be present and functional on the monitored server. For details, refer to section 6. Known Issues/Limitations, in the accompanying vrealize Operations Management Pack for Microsoft SQL Server Release Notes. 2.1 Setting MS SQL User Privileges To set up the minimum SQL user permissions needed for an MS SQL Management Pack monitoring user, complete the following tasks: NOTE: It is recommended to complete this process prior to installing and configuring the Management Pack. You should use your own MS SQL credentials (login), user, and role names. 1. Grant your MS SQL login credentials VIEW ANY DEFINITION, VIEW SERVER STATE permissions. 2. Next, to ensure all future-created databases are monitored, create a user that maps to your MS SQL credentials and has the db_datareader role on the following databases: each user database msdb database model database 3 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

4 3. Licensing Requirements When purchased individually, the Management Pack for Microsoft SQL Server is licensed per Microsoft SQL Server instance. Alternatively, customers who have purchased Blue Medora s True Visibility Suite (Standard, Advanced, or Enterprise) can access all management packs within that suite (and the edition below it, if applicable). The Management Pack for Microsoft SQL Server is part of Blue Medora s Enterprise True Visibility Suite (TVS), which means a TVS Enterprise license is required to use it. For more information, visit A license key will be provided by Blue Medora when the Management Pack or True Visibility Suite is purchased and must be added as a Microsoft SQL Server License within vrealize Operations before the Management Pack can be configured and used. Refer to section 5.2 Adding a License Key, for details. 4. Upgrading the Management Pack Before upgrading to a newer version of the Management Pack (i.e., uploading a new.pak file), we recommend the following clean-up tasks: Delete existing dashboards Delete existing adapter instance(s) and objects 4.1 Deleting existing dashboards within vrealize Operations If you do not remove the dashboards from a previous version of the Management Pack before upgrading, you will see duplicate Microsoft SQL Server dashboards in the Dashboard List drop-down menu after installation. To remove existing Management Pack dashboards: 1. Navigate to Content > Dashboards. 2. Multi-select all Microsoft SQL Server dashboards. 3. Click Delete Dashboard. 4. Click Yes when the confirmation dialog box appears to delete the selected dashboards. Figure 1: Delete Dashboards 4 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

5 4.2 Deleting existing adapter instance(s) and objects You must also remove previous adapter instance(s) and their related objects, as the old instance(s) will not collect data and creating new instances makes new related objects instead of using existing objects. After deleting existing dashboards and installing the new version of the Management Pack, remove the previous adapter instance(s) and their related objects, then configure the new adapter instance(s). To remove existing Management Pack adapter instance(s) and objects: 1. Log in to vrealize Operations as an administrator. 2. Click on the Administration navigation shortcut ( ). The Solutions view should automatically open. 3. Select Microsoft SQL Server from the Solutions list. 4. Click the Configure icon ( ). The Manage Solution window will appear. 5. Select an instance from the list on the left and click the Delete icon ( ). 6. Click the Remove related objects checkbox in the dialog that appears (refer to Figure 2), then click Yes. Figure 2: Delete Previous Adapter Instance(s) and Objects 5 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

6 5. Installing the Management Pack Installing the Management Pack in vrealize Operations involves completing the following tasks: Uploading the Installation File Adding a License Key 5.1 Uploading the Installation File The Management Pack for Microsoft SQL Server is installed using a.pak file Prerequisites Obtain the Management Pack installation file from Read the release notes that are included with the.pak file Procedure 1. Save the.pak file in a temporary location. 2. Log in to vrealize Operations as an admin user. 3. Click the Home icon, then select the Administration navigation shortcut from the panel on the left. Figure 3: Home > Administration 6 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

7 4. In the right panel, the Solutions tab will be displayed. Figure 4: Solutions Tab 5. Click the Add icon ( ) to upload the.pak file to the vrealize Operations server. In the dialog that appears, browse to the location of the saved.pak file, then click Upload. NOTE: The.pak file upload may take several minutes to complete. Status information appears in the Installation Details text box throughout the installation process. Figure 5: Select the.pak file to upload 7 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

8 6. Click Next when the upload has finished. Read the End User License Agreement (EULA) and click the I accept the terms of this agreement checkbox to accept, then click Next. 7. Click Finish when the installation process is complete. NOTE: The installation utility creates the sql_server_adapter folder and sql_server_adapter.jar file in the $VCOPS_BASE/user/plugins/inbound folder. Refer to section 7. Appendix I: Management Pack Folders and Files for more information. 5.2 Adding a License Key The Management Pack requires a valid license for full operation. Complete the following steps to license the Management Pack. 1. In vrealize Operations Manager, navigate to Administration > Licensing > License Keys. 2. Click the Add icon ( ). In the dialog that appears, select Microsoft SQL Server. Figure 6: Add License 3. Enter your Blue Medora license key, then click Validate. If successful, License key validated successfully will be displayed. 4. Click Save to finish adding your license key. 8 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

9 6. Configuring the Management Pack Configuring the Management Pack for Microsoft SQL Server includes the following tasks: Creating an Adapter Instance and Credential Manually Discovering Resources (if necessary) Validating Management Pack Data Collection 6.1 Creating an Adapter Instance and Credential You must create an adapter instance and credential for the Management Pack in order to define the adapter type and identify the host from which the adapter instance will retrieve data. NOTE: For full coverage of Always On Availability Group health and status, create adapter instances pointing to each individual replica (host) and ensure Autodiscovery is set to True. This will allow the Management Pack to monitor both the primary and secondary replica health statuses, and provide as much visibility as possible Prerequisites Install the Management Pack for Microsoft SQL Server. Refer to section 5. Installing the Management Pack Procedure 1. Log in to vrealize Operations as an administrator. 2. Click on the Administration navigation shortcut ( ). The Solutions view should automatically open. 3. Select Microsoft SQL Server from the Solutions list. Figure 7: Solutions List 9 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

10 4. Click the Configure icon ( ). The Manage Solution window will appear. Figure 8: Manage Solution Window NOTE: If creating multiple adapter instances, click the Add icon ( ) above the list of Instance Names on the left. 5. In the Manage Solution window, enter the following information: Instance Settings: Display Name: A name for this particular instance of the Management Pack Description: Optional; most helpful for describing multiple adapter instances of the Management Pack Basic Settings: Host: Hostname of MS SQL Server instance NOTE: The Management Pack supports IPv4 and IPv6. IPv6 can be used via a Fully Qualified Domain Name that routes to IPv6, but direct IPv6 addresses are not supported. Instance: Name of MS SQL Server instance that is running; default is MSSQLSERVER Credential: Click the Add icon ( ), then select the credential type (refer to Figure 9). 10 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

11 Advanced Settings: Collector: Automatically selected Port: Optional; specify to ensure you are connecting to the intended instance Active Query Resources: Allows you to specify the number of queries returned per collection; default value is 10, but can be modified Maximum Query Resources: Allows you to specify the maximum number of queries to keep in your vrops environment; default value is 100, but can be modified Support Autodiscovery: Default setting is True, which enables the adapter instance to create resources for you. If you select False, you must manually discover your Microsoft SQL Server resources. Figure 9: Manage Credential Credential Name: A name for this set of Management Pack credentials User Name: MS SQL User Name Password: MS SQL Password NOTE: vcenter credentials are optional and may be used to connect to the vcenter API, which allows the Management Pack to make MS SQL Server Instance to VM relationships via a secondary MAC address. 6. Click OK to save your credential. 7. Click Test Connection to ensure vrealize Operations can connect properly to the server(s). 8. Click Save Settings to save your adapter instance configuration. 11 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

12 6.2 Manually Discovering Resources If Autodiscovery was set to False when configuring the adapter instance, you will need to manually discover resources as described in this section. With manual discovery, the adapter sends a request to the server to return resources, which you then manually select to import into vrealize Operations Prerequisites Create a Microsoft SQL Server adapter instance and credential. Refer to the previous section 6.1 Creating an Adapter Instance and Credential, for details Procedure 1. Log in to vrealize Operations as an administrator. 2. Click the Administration navigation shortcut ( ). 3. Click Inventory Explorer in the navigator pane. Figure 10: Inventory Explorer > Adapter Types 4. Under Adapter Types, select Microsoft SQL Server Adapter. 5. Click the Discover Resources icon ( ) to open the Discover Objects window. Figure 11: Discover Objects Window 6. In the Discover Objects window, select the following information: The Collector to use NOTE: Unless you added additional collectors, the only available collector is your vrops server. Microsoft SQL Server Adapter for Adapter Type The applicable Adapter Instance Microsoft SQL Server Discovery for Discovery Info Whether Only New Objects (select/de-select checkbox) should be collected 12 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

13 7. Click OK to start the discovery process. 8. The discovery process can take several seconds to several minutes. When it has finished, the Discovery Results window lists your resources. 9. Double-click each resource kind that contains resources to add. 10. Select options for each kind of resource. Refer to Table 3. Table 3: Resource Options OPTION Import Collect DESCRIPTION Import the resources but do not start collecting data. Resources appear in the resource list as Not Collecting; data is not stored; analysis is not performed. Import the resources and start collecting data. When you select the Collect check box, the Import check box is also selected. 11. Click OK. The Discovery Results window closes and the new resources appear What To Do Next If you did not select the option to start metric collection when you defined a resource, you can start metric collection after the resource is defined. To start collecting metrics for a resource, select the resources, then click the Start Collecting icon ( ). 6.3 Configure the Properties File There are two settings embedded within the properties file that can be modified to configure the Management Pack for your particular preferences. The following settings can be found in the microsoftsqlserver.properties file within the sql_server_ adapter/conf/ folder. You can modify the entries in the file, re-save the file, and they will be read in during the next collection. maximum_number_of_events_to_return_per_collection= Description: This setting limits the total number of events returned per collection cycle. The default setting is blank, which returns all events. exclude_event_queries=true Description: This setting disables events that require intensive queries that may adversely affect your environment. If this property is set to false, you will be able to get events related to fragmentation and indexing. NOTE: After upgrading the Management Pack, if this setting is changed to false, event queries will be enabled and the events will re-fire. 13 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

14 6.4 Validate Data Collection After you add a Microsoft SQL Server adapter instance, you will want to validate the data that it collects in vrealize Operations Prerequisites Add a Microsoft SQL Server adapter instance. Refer to section 6.1 Creating an Adapter Instance and Credential, for details Procedure 1. Select the Environment shortcut. NOTE: If you enabled Autodiscovery for the adapter instance, it will create resources as soon as it begins collecting metrics. If you disabled Autodiscovery for the adapter instance, you must go back and discover resources manually before you can validate data collection. Refer to section 6.2 Manually Discovering Resources. 2. Under Inventory Trees, select All Objects, then expand the Microsoft SQL Server Adapter objects list. 3. Select a resource from the list, then click the Troubleshooting tab and All Metrics view to validate values against the data source. Figure 12: Microsoft SQL Server Adapter Objects Troubleshooting 14 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

15 7. Appendix I: Management Pack Folders and Files The installer places the Management Pack files in the sql_server_adapter folder under the $VCOPS_BASE/ user/plugins/inbound folder as shown below. Table 4: Management Pack Folders and Files FOLDER FILE DESCRIPTION conf lib work #_SqlServerAdapter_max_ observations.moar dashboards (folder) describe.dtd describe.xml file_migration.py historical.properties images (folder) license.properties microsoftsqlserver.properties oss_attribution.txt reports (folder) reskndmetrics (folder) resources (folder) scripts (folder) version.txt views (folder) Refer to lib folder for entire list install.log lastcollection_#.properties Tracks Max Observed metrics for the adapter instance Contains.json files for Management Pack Dashboards Used to validate describe.xml Describes the Management Pack Copies files from old installation of the Management Pack to the new directory Used to enable historical mode. Allows the adapter to backfill data if collection is interrupted for any reason. Contains.png files for AdapterKind, ResourceKind, and TraversalSpec Contains back-up copy of licenses used for this Management Pack Contains properties that can be modified to adjust adapter operation Describes open source libraries used by the Management Pack Contains.xml files for Management Pack Reports Contains.xml files for Dashboard Metric configuration Contains resources.properties file Contains.sdm files consumed by the Management Pack Contains version information Contains.xml files for Management Pack Views.jar files that contain the classes and resources used to implement the Management Pack Tracks when the last collection for each adapter instance was performed (used when historic mode is enabled) 15 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

16 8. Appendix II: Revision Notes This installation guide is updated with each release of the product, or when necessary. The following table provides its revision history. REVISION DATE DESCRIPTION REV-06 REV-05 REV-04 REV-03 REV DEC SEP AUG MAR JAN-2016 Updated Table 1: Management Pack Installation & Configuration Requirements to reflect current Management Pack requirements Removed section Windows Authentication Requirements Added section 4. Upgrading the Management Pack Updated section 6.1 Creating an Adapter Instance and Credential to reflect changes made to the settings and credential fields Added section 6.3 Configure the Properties File Updated section 7. Appendix I: Management Pack Folders and Files to show current Management Pack files Updated screenshots throughout the document Added required default instance information to the note under Table 1: Management Pack Installation & Configuration Requirements Added information to section 3. Licensing Requirements about Blue Medora s True Visibility Suite Reformatted section 6. Configuring the Management Pack to combine previous sections Add a Credential and Add an Adapter Instance into section 6.1 Creating an Adapter Instance and Credential Added default port information to Table 1: Management Pack Installation & Configuration Requirements Updated section Add an Adapter Instance to include default port information Moved section Performing Actions to vrealize Operations Management Pack for Microsoft SQL Server User Guide Reformatted section 2. Installation and Configuration Requirements Added section Setting MS SQL User Privileges REV JUN-2015 Initial release 16 vrealize Operations Management Pack for Microsoft SQL Server Installation & Configuration Guide

17 You can find the most up-to-date technical documentation on the Blue Medora support site at: The Blue Medora website also provides the latest product updates. If you have comments about this documentation, submit your feedback to: Copyright 2016 Blue Medora Inc. All rights reserved. U.S. and international copyright and intellectual property laws protect this product. Blue Medora is a registered trademark or trademark of Blue Medora in the United States and/or other jurisdictions. The Microsoft name (including Microsoft SQL Server) and logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Blue Medora 3225 N Evergreen Dr. NE Suite 103 Grand Rapids, MI bluemedora.com