HP StorageWorks. HP PolyServe Software for Microsoft SQL Server administration guide. HP PolyServe Software for Microsoft SQL Server 4.0.

Transcription

1 HP StorageWorks HP PolyServe Software for Microsoft SQL Server administration guide HP PolyServe Software for Microsoft SQL Server Part number: T First edition: February 2010

2 Legal and notice information Copyright 2004, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

3 Contents 1 Introduction... 9 Virtual SQL Servers... 9 Active-Passive architecture... 9 Plan Your SQL configuration Active-Active Many-to-One SQL monitors and failover What happens during a failover? Replication of registry keys Virtual MSDTC Virtual SSAS Install SQL Server instances SQL Server installation overview SQL Server and operating system support General prerequisites Supported number of SQL instances Installation considerations for SQL Server Installation prerequisites Using Mixed Mode authentication Template file IP network configuration Virtual MSDTC Instance-Aware and Non-Instance-Aware components Instance ID File streaming implications Account provisioning Set permissions on existing PSFS filesystems SQL Server 2008 references Installation considerations for SSAS 2008 instances Installation considerations for SQL Server Template file IP network configuration SQL Server 2005 SP2 required for Full Text Search Virtual MSDTC Instance-Aware and Non-Instance-Aware components Set permissions on existing PSFS filesystems Installation considerations for SSAS 2005 instances Run the Multi-Node Install Wizard for SQL Server Install SQL Server 2008 instances Install SQL Server 2005 instances Other installation tasks Adjust the Maximum Memory setting for SQL Server Requirement for BUILTIN\Administrators group TCP/IP Assignments on backup nodes HP PolyServe Software for Microsoft SQL Server administration guide 3

4 3 Upgrade SQL Server/SSAS 2005 instances in place Prepare for the upgrade Supported upgrades Prerequisites SQL Server 2008 prerequisites In-place upgrade prerequisites Restrictions Run the Multi-Node In-Place Upgrade Wizard Start the In-Place Upgrade Wizard Select the Microsoft product to upgrade dialog Installation Credentials dialog Select the Instances to Upgrade dialog Select Template File dialog Move Virtual SQL Servers/Virtual SSAS to operate mode Add, edit, or delete products Update SQL Server instances Update overview Location of service packs and hotfixes Maintenance mode is required for update operations Update considerations for SQL Server Extract zip files Service pack and hotfix names Use of a hidden administrative share Update considerations for SQL Server Instance-Aware components Extract zip files SQL Server 2005 SP2 required for Full Text Search SQL Server 2005 hotfix Service pack and hotfix names Use of a hidden administrative share Installation log files Run the Multi-Node Update Wizard for SQL Server Configure Virtual SQL Servers Configure Virtual SQL Servers DNS requirement for Virtual SQL Servers Create a Virtual SQL Server Progress reports Add a Virtual SQL instance View the Virtual SQL instances Advanced options for monitors Policy Scripts Use custom scripts to modify Start/Stop activities Event severity Script ordering Configure SQL clients Rehost a Virtual SQL Server Performance monitoring with perfmon Other SQL Server procedures Maintenance mode Create a notifier for the Registry Replicator

5 Change the network configuration Add a new node to a Virtual SQL Server Virtual SQL Server procedures Modify the configuration Virtualize or devirtualize MSDTC Enable/disable a Virtual SQL Server Delete a Virtual SQL Server View status for a Virtual SQL Server Remove from Server option Virtual SQL instance procedures Modify the configuration Disable or enable a SQL service monitor Clear monitor errors Delete a Virtual SQL instance Revirtualize a Virtual SQL instance View status for a Virtual SQL instance SQL Agent Stop the SQL Service Database backups Configure SQL Mail and SQL Agent Mail Uninstall SQL Server instances Configure Virtual MSDTC Overview DNS requirement for the Virtual MSDTC DTC transaction statistics Create a Virtual MSDTC Progress reports Add the Virtual MSDTC Service Actions when configuring the Virtual MSDTC Service Configure other nodes for Virtual MSDTC Rehost a Virtual MSDTC Other Virtual MSDTC procedures Add a new node to a Virtual MSDTC Virtual MSDTC procedures Modify the configuration Enable/disable a Virtual MSDTC Delete a Virtual MSDTC View status for a Virtual MSDTC Virtual MSDTC Service procedures Modify the configuration Disable or enable a Virtual MSDTC Service Remove a Virtual MSDTC Service Remove a server from the Virtual MSDTC Service View Alerts for the Virtual MSDTC Service Clear a monitor error for the Virtual MSDTC Service View status for the Virtual MSDTC Service Configure SQL Server Analysis Services Overview Configure a Virtual SSAS DNS requirement for Virtual SSAS Create a Virtual SSAS Progress reports HP PolyServe Software for Microsoft SQL Server administration guide 5

6 Add a Virtual SSAS instance Monitoring Virtual SSAS instances SQL Server Profiler Surface Area Configuration tool Performance monitoring with perfmon Rehost a Virtual SSAS Other Virtual SSAS procedures Maintenance mode Add a new node to a Virtual SSAS Virtual SSAS procedures Modify the configuration Enable/disable a Virtual SSAS Delete a Virtual SSAS View status for a Virtual SSAS Virtual SSAS instance procedures Modify the configuration Disable or enable a Virtual SSAS instance Clear monitor errors Delete a Virtual SSAS instance Revirtualize a Virtual SSAS instance View status for a Virtual SSAS instance Using the Applications tab Overview SQL resources on the Application tab Virtual SQL Servers and Virtual SQL instances Virtual MSDTC and Virtual MSDTC Service Virtual SSAS and Virtual SSAS instances Monitor errors Manage the SQL configuration Drag and drop Caution when using drag and drop Select tasks from a menu Virtual SQL Servers and Virtual SQL instances Virtual MSDTC and Virtual MSDTC Service Virtual SSAS and Virtual SSAS instances Instance Aliasing Overview Instance Aliasing port considerations Move the mapping file Configure Instance Aliasing Configure Instance Aliasing settings Map default instances Map named instances Modify Instance Aliasing mappings Delete Instance Aliasing mappings Recommendations for monitoring Instance Aliasing Create a linked server Troubleshooting Install/uninstall issues SQL Server 2005 installation takes too long

7 Installations via a Microsoft Terminal Services client Installer reports a failure SQL Server 2005 core and components SQL Server 2005 service packs and hotfixes Uninstall issues Connection issues DNS misconfiguration causes connection failure References queryspn.vbs script Connection error with Windows authentication Windows authentication fails with SQL Server replication Cannot authenticate on the local machine with a virtual host name Error when creating a Virtual SQL Server Failure to virtualize a SQL instance Cannot access a Virtual SQL instance from the active node SQL Server 2005 instance does not start Virtualized SSAS instance does not start and reports an invalid request address Error when creating a distributor for replication Upgrade production SQL Servers General upgrade process Plan the upgrade Test the upgrade Back up the current machine state Notify users of upgrade start Apply the upgrade Confirm the upgrade Notify users of upgrade completion Back up the machine state Upgrade SQL instances Upgrade considerations Upgrade procedure Multiple instance upgrades General machine upgrades A Configure SQL Server Reporting Services Configure Reporting Services Configure Report Server for SQL Server Configure Report Server for SQL Server Configure high availability support B Hosting Configurations for MS DTC Overview Set up local MS DTC-enabled Virtual SQL Servers Set up a remote node for hosting DTC Set up local nodes to use Remote DTC Summary References C Support and other resources HP technical support Subscription service HP websites HP PolyServe Software for Microsoft SQL Server administration guide 7

8 Index

9 1 Introduction HP PolyServe Software for Microsoft SQL Server (HP PolyServe Software) provides high availability for SQL Server databases located on PSFS cluster filesystems. High availability support is also provided for MS DTC and Microsoft SQL Server 2005/2008 Analysis Services. Virtual SQL Servers HP PolyServe Software uses Virtual SQL Servers to provide failover support and high availability. A Virtual SQL Server virtualizes the network name and IP address associated with a particular SQL Server/Instance. That is, rather than using the network name and IP address of an actual server, a Virtual SQL Server is created and assigned a unique name/ip-address pair. Up to 16 SQL instances can be associated with each Virtual SQL Server. Clients access the databases associated with an instance via the Virtual SQL Server name or IP address; they do not need to know which node is running the SQL instance. When you configure a Virtual SQL Server, you will need to specify an active, or primary, node and one or more passive, or backup, nodes. The SQL instances associated with the Virtual SQL Server must be installed on all of these nodes. The Virtual SQL Server is active on the primary node, and SQL database requests are serviced from there. On failure, the ClusterPulse process (provided with Matrix Server) will fail over, or migrate, the Virtual SQL Server to one of the designated backup servers, where it will continue to provide access to the same PSFS filesystem data under the same name/ip-address pair. Active-Passive architecture HP PolyServe Software uses an Active-Passive architecture for high-availability. For example, when you virtualize a SQL server instance in a two-node cluster, you declare one node to be the active, or primary, node for the instance and the second node to be the backup. The high-availability engine provided with HP PolyServe Software for Microsoft SQL Server then creates the appropriate profiles for the virtualized instance. A profile is a container consisting of the SQL data (that is, databases and logs) and the corresponding registry setting necessary for starting an instance of SQL Server. The Active-Passive architecture uses an N+1 model in which there is a local profile (an N profile ) for each node participating in the Virtual SQL Server plus a cluster profile (the + profile) that runs on the active node for the Virtual SQL Server. For example, in a two-node cluster there are three profiles: the two local profiles (N) and a clustered profile (+1). The clustered profile can move around the cluster, and when mounted on a node, it turns the state of the node from passive to active. At any one point in time, the node running with the clustered profile (the +1 profile) is the active node and all other nodes are passive (that is, running with their local N profiles). On the PolyServe Management Console, the active node is specified as the primary node and the passive nodes are specified as backup nodes. Throughout this guide, the primary and backup designations are used to refer to the active and passive nodes. HP PolyServe Software for Microsoft SQL Server administration guide 9

10 Plan Your SQL configuration Before installing SQL Server, it is important to determine how the SQL Server instances should be configured across the matrix. First determine the number of SQL instances that you will need. These instances can be installed on any node in the matrix. Next, determine how you want to associate the instances with Virtual SQL Servers. You could use a separate Virtual SQL Server for each instance, you could assign all of the instances on a node to a single virtual server, or you could use some other scheme. Then determine how you want to configure the Virtual SQL Servers. Each Virtual SQL Server needs a primary node and one or more backup nodes. The backup nodes for each Virtual SQL Server must contain the same set of SQL instances as the primary node. Following are some sample configurations. NOTE: A primary SQL instance and its backup SQL instances must have the same name. For example, if you install an SQL instance called instance1 on the primary node, you will also need to install an instance called instance1 on the backup node. Active-Active In this configuration, the nodes in the matrix back up each others Virtual SQL Servers. In the following example, the Virtual SQL Server virtual1 is primary on node1 and has a backup on node2. The SQL instance instance1 is associated with this virtual server and exists on both nodes. Clients can access the virtual server using virtual1\instance1. Similarly, Virtual SQL Server virtual2 is primary on node 2 and has a backup on node1. Two instances (instance2 and instance3) are associated with this virtual server and exist on both nodes. Many-to-One In this configuration, one node provides backups for the Virtual SQL Servers running on the other nodes. In the following example, nodes 1, 2, and 3 are each hosting a Virtual SQL Server. These virtual servers all use node 4 as a backup. The instances associated with the Virtual SQL Servers are all installed on backup node Introduction

11 The following configuration also has one node providing a backup for the Virtual SQL Servers on other nodes. In this example, the SQL instances associated with the Virtual SQL Servers all have the same name, instance1. This configuration supports only one failover at a time. If the Virtual SQL Server on node 1 ( virtual1 ) fails over and node 2 then goes down, the Virtual SQL Server on node 2 ( virtual2 ) will not be able to fail over. This occurs because instance1 on node 4 is currently providing access to the databases for the instance1 associated with the Virtual SQL Server virtual1. A similar situation occurs when a Virtual SQL Server is moved to maintenance mode (for example, to apply a service pack). In maintenance mode, all SQL instances associated with the Virtual SQL Server are shut down on the primary and backup nodes. In the above example, if the Virtual SQL Server on node 1 ( virtual1 ) is moved to maintenance mode, instance1 on node 1 and also its backup instance1 on node 4 will be shut down. There is now no backup available for instance1 on node 2 and node 3. To minimize the time without a backup, HP recommends that you perform the maintenance on the backup instance first and then reenable it. The backup instance will then be available for the other primary instances. SQL monitors and failover When you add a SQL instance to a Virtual SQL Server, HP PolyServe Software creates a service monitor for that instance. The monitor is active on the node currently hosting the Virtual SQL Server and periodically determines whether the SQL service is up. If the monitor detects that the SQL service is down, HP PolyServe Software can attempt to restart the service. (When you create the monitor, you can specify the number of times that HP PolyServe Software should try to restart the service.) If the attempts are not successful, by default the Virtual SQL Server will fail over to a backup node. You can customize the failover behavior for each SQL service monitor. For example, you can use the Policy configuration option to specify whether the Virtual SQL Server should fail back to the original node or remain on the backup node after the problem causing the failover has been corrected. What happens during a failover? Failovers can be planned (for example, upgrading the operating system) or unplanned (such as a crash of a primary node). HP PolyServe Software takes these actions during a failover: HP PolyServe Software for Microsoft SQL Server administration guide 11

12 Removes the IP address for the Virtual SQL Server from the original node and then adds it to the backup node. Updates registry keys and then starts SQL Server and SQL Agent on the backup node. Clients using the IP address of the Virtual SQL Server will now access the databases on the PSFS filesystem via the SQL instance on the backup node. After a Virtual SQL Server fails over, by default it remains on the backup node. (Optionally, you can configure the Virtual SQL Server to automatically fail back to the original node.) Replication of registry keys HP PolyServe Software replicates the registry keys for the SQL server from the local machine to a location on the PSFS filesystem containing the corresponding master SQL databases. The replicator watches the main SQL instance key and, if it changes, persists the key to the shared filesystem. If a Virtual SQL Server fails over to a backup node, that node reads the keys from the PSFS filesystem and applies them back before starting SQL services. On failback, after SQL services are stopped on the backup node, the registry is returned to its original state on that node. Virtual MSDTC HP PolyServe Software provides high availability support for Microsoft Distributed Transaction Coordinator (MS DTC), the transaction manager responsible for coordinating transaction atomicity across multiple resource managers. A Virtual MSDTC is configured on at least two cluster nodes, with one node serving as the primary and the other nodes as backups. MS DTC is accessed via the Virtual MSDTC. If a problem occurs on the primary node, the Virtual MSDTC can fail over to a backup node, which will continue the MS DTC operations. See Chapter 6 on page 77, for more information about configuring MS DTC for high availability. MS DTC can also be managed by a Virtual SQL Server, as in previous releases of this product. Virtual SSAS HP PolyServe Software includes high availability support for Microsoft SQL Server 2005/2008 Analysis Services (SSAS) instances, which provide online analytical processing (OLAP) and data mining features. A Virtual SSAS is configured on at least two cluster nodes, with one node serving as the primary and the other nodes as backups. SSAS instances are then associated with the Virtual SSAS. The SSAS instances are accessed via the Virtual SSAS. If a problem occurs on the primary node, the Virtual SSAS can fail over to a backup node, which will then provide access to the SSAS instances. See Chapter 7 on page 89, for more information about configuring SSAS for high availability. 12 Introduction

13 2 Install SQL Server instances This chapter describes how to install SQL Server 2005 and 2008 instances. You can also install SSAS 2005 and 2008 instances. SQL Server installation overview Before starting the installation, you should be aware of the following. SQL Server and operating system support HP PolyServe Software can be used with SQL Server 2005/2008 Standard and Enterprise Editions (32-bit and 64-bit). Windows 2008 SP2, 64-bit, is the supported operating system. General prerequisites Before installing SQL Server, the following prerequisites should be met: PolyServe Matrix Server must be installed on each node. You will also need to create PSFS cluster filesystems to store the SQL databases. The filesystems must use the 8 KB block size. If you will be using a PSFS filesystem created under Matrix Server 3.2 or earlier, you will need to enable sparse files on the filesystem. Use the following command to do this. (In the command, <device> can be a drive letter, a mount point, or a psd or psv name.) psfscheck --enable-sparse <device> Microsoft Cluster Services (MSCS) must not be installed. For SQL Server 2005, the Microsoft.NET Version 2.0 framework must be installed on all nodes. For SQL Server 2008,.NET framework 3.5 must be installed. If you will be installing SQL Server Reporting Services, be sure to install the ISS and ASP.NET components first, as described in Microsoft Knowledge Base article : SQL Server and the SQL Agent can be configured to use either the Local System account or a Domain account. However, certain SQL Server features are not available if you use the Local System account. Consult the Microsoft documentation for more information about these accounts and the features they support. Multiple instances per node are supported. A primary SQL instance and its backup SQL instances must have the same name. For example, if you install a SQL 2008 instance called instance1 on the primary node, you will also need to install a SQL 2008 instance called instance1 on the backup node. Supported number of SQL instances HP PolyServe Software supports up to 50 SQL Server 2005/2008 instances per node. HP PolyServe Software for Microsoft SQL Server administration guide 13

14 Installation considerations for SQL Server 2008 Installation prerequisites The following software must be installed on the cluster nodes before installing SQL Server instances: Windows 2008 SP2, 64-bit Windows Installer 4.5.NET framework 3.5 (SP1) Windows PowerShell 1.0 The PolyServe SQL Browser must be stopped during the instance installation to avoid UDP port 1434 collision. NOTE: HP recommends that you run the SQL 2008 setup manually once per node. As soon as all the prerequisites are installed on the node, you can cancel the setup without first completing a SQL Server instance installation. Using Mixed Mode authentication SQL Server 2008 requires that a strong SA password be specified at installation time. The criteria for a strong password includes the following requirements: The password must be more than 8 characters in length. The password must contain both uppercase and lowercase letters. The password must contain numbers or non-alphanumeric characters such as #, %, or ^. For more information, see the following Microsoft article: Template file The Multi-Node Installer creates an INI template file that is used in the installation. This file should be saved in a location that provides read access for all nodes. The installer encrypts passwords in the file using a HP PolyServe algorithm. HP recommends that you use filesystem permissions to restrict access to template files. IP network configuration The SQL Server 2008 instance installation captures and stores the current IP network configuration of the node on which it is installed. If you later need to change the network configuration (for example, to remove a NIC or change its IP), it is necessary to devirtualize the Virtual SQL Servers on the affected node, make the needed changes, and then revirtualize the Virtual SQL Servers. Virtual MSDTC SQL Server instances cannot be installed on nodes configured for Virtual MSDTC. The installation will fail on these nodes. 14 Install SQL Server instances

15 Instance-Aware and Non-Instance-Aware components The SQL Server 2008 package includes both Instance-Aware and Non-Instance-Aware components. The Instance-Aware components should be installed and managed by reference to the name of the instance (or simply the server name if the Default instance is used). The Non-Instance-Aware components are installed once per server and shared by all instances active on that server. The Instance-Aware components are: Database Engine. The Default or named instance itself. Full Text Search Engine. A child instance-aware service installed only if the Database Engine is installed on the node. Analysis Services. A separate service that does online data analysis for data mining and reporting. Reporting Services. The server and client components required to do reporting and data presentation development. Server Agent. The service that handles the management and maintenance jobs for the instance. We recommend that you install the Non-Instance-Aware components only once per server. Any future install templates should not include these components. After each installation, check the logs for information such as whether a reboot is necessary. The following Books On Line (BOL) article provides a summary of the issues associated with installing multiple instances on a single node: The next article lists the default file locations for all components of a SQL Server instance and explains concepts for the installed instances of the Database Engine, Analysis Services, and Reporting Services. As you review this article, note that moving the installed data file directories for the configurable components has not been tested with HP PolyServe Software; however, as long as the configuration is identical for an instance across all nodes, it should be functional. The following article contains tables listing the directory structure and configurable components: The following article discusses installing components. Be sure to review the footnotes for the table. Also note that installing both 32-bit and 64-bit Reporting Services on a node running a 64-bit operating system is not supported by Microsoft or HP PolyServe Software. Instance ID SQL Server 2008 provides an Instance ID that is used to identify installation directories and registry keys for a particular instance. By default, the instance ID is the same as the instance name. You can specify a different ID if desired when you install an instance. File streaming implications Although the SQL Filestream can be enabled during an installation of SQL 2008, the actual BLOB cannot be put on an HP PolyServe clustered filesystem (PSFS). HP PolyServe Software for Microsoft SQL Server administration guide 15

16 Account provisioning In SQL Server 2005, the Windows Builtin\Administrator local group was automatically given administrative permissions for the SQL instance. This is no longer the case with SQL Server Instead, when you install an instance, you will need to specify the users and/or groups that should have administrative permissions (sysadmin) for the instance. Set permissions on existing PSFS filesystems If you will be installing a SQL 2008 instance on a mountpoint for a PSFS filesystem created under Matrix Server 3.2 or earlier, the installation may fail if the file permissions are not set appropriately. You can use any of the following methods to set the permissions if necessary. Mount the filesystem as a drive letter (for example, s:\). In Windows Explorer, open the Properties for the volume and select the Security tab. Then set the permissions to Full Control for Administrators/users. Mount the filesystem as a mountpoint such as c:\psfs\psd15p1. In Windows Explorer, open the Properties for the folder, go to the Mounted Volume properties (this is not the same as the folder security), and set the permission for Administrators/users to Full Control. Use the cacls.exe utility to give the local Administrators group full control and to give Everyone read-only permissions. In the following command, %1 is the mounted folder. cacls %1 /t /m /p Administrators:F Everyone:R For example: cacls c:\psfs\psd1p1 /t /m /p Administrators:F Everyone:R NOTE: If you are installing a retail version of SQL Server, be sure to enter the product key provided with your software. The product key is required for all retail versions of SQL Server. If you do not specify a product key, the installer will add a sample product key ( PID= ABCD ) to the template.ini file. However, MSDN versions of SQL Server already have the product keys embedded in the installation files. SQL Server 2008 references The following Microsoft documentation provides more information about SQL Server SQL Server 2008 Books Online: How to install SQL Server: Features supported by Editions of SQL Server 2008: SQL Filestream: Microsoft.NET Framework 3.5: 16 Install SQL Server instances

17 Windows Installer 4.5: Windows Powershell: Installation considerations for SSAS 2008 instances SSAS 2008 instances are installed through the SQL Server 2008 instance installation procedure (see Install SQL Server 2008 instances on page 19). When you create a template for the installation, select Analysis Services on the Template Features Wizard screen. The SSAS instance will then be installed. SSAS instances can be installed as part of a SQL Server instance installation, or you can install just the SSAS instance. Installation considerations for SQL Server 2005 Template file The Multi-Node Installer creates an INI template file that is used in the installation. This file should be saved in a location that provides read access for all nodes. The installer encrypts passwords in the file using a HP PolyServe algorithm. HP recommends that you use filesystem permissions to restrict access to template files. IP network configuration The SQL Server 2005 instance installation captures and stores the current IP network configuration of the node on which it is installed. If you later need to change the network configuration (for example, to remove a NIC or change its IP), it is necessary to devirtualize the Virtual SQL Servers on the affected node, make the needed changes, and then revirtualize the Virtual SQL Servers. SQL Server 2005 SP2 required for Full Text Search SQL Server 2005 SP2 is required if you will be using FTE. SP2 provides the NTLM Security Support Provider (NTLMSSP) service, which is used by FTE. Because Windows Server 2008 does not include the NTLMSSP service, FTE will fail if SP2 is not installed. Virtual MSDTC SQL Server instances cannot be installed on nodes configured for Virtual MSDTC. The installation will fail on these nodes. Instance-Aware and Non-Instance-Aware components The SQL Server 2005 package includes both Instance-Aware and Non-Instance-Aware components. The Instance-Aware components should be installed and managed by reference to the name of the instance (or simply the server name if the Default instance is used). The Non-Instance-Aware components are installed once per server and shared by all instances active on that server. HP PolyServe Software for Microsoft SQL Server administration guide 17

18 The Instance-Aware components are: Database Engine. The Default or named instance itself. Full Text Search Engine. A child instance-aware service installed only if the Database Engine is installed on the node. Analysis Services. A separate service that does online data analysis for data mining and reporting. Reporting Services. The server and client components required to do reporting and data presentation development. Server Agent. The service that handles the management and maintenance jobs for the instance. We recommend that you install the Non-Instance-Aware components only once per server. Any future install templates should not include these components. After each installation, check the logs for information such as whether a reboot is necessary. The following Books On Line (BOL) article provides a summary of the issues associated with installing multiple instances on a single node: The next article lists the default file locations for all components of a SQL Server instance and explains concepts for the installed instances of the Database Engine, Analysis Services, and Reporting Services. As you review this article, note that moving the installed data file directories for the configurable components has not been tested with HP PolyServe Software; however, as long as the configuration is identical for an instance across all nodes, it should be functional. The following article contains tables listing the directory structure and configurable components: The following article discusses installing components. Be sure to review the footnotes for the table. Also note that installing both 32-bit and 64-bit Reporting Services on a node running a 64-bit operating system is not supported by Microsoft or HP PolyServe Software. Set permissions on existing PSFS filesystems If you will be installing a SQL 2005 instance on a mountpoint for a PSFS filesystem created under Matrix Server 3.2 or earlier, the installation may fail if the file permissions are not set appropriately. You can use any of the following methods to set the permissions if necessary. Mount the filesystem as a drive letter (for example, s:\). In Windows Explorer, open the Properties for the volume and select the Security tab. Then set the permissions to Full Control for Administrators/users. Mount the filesystem as a mountpoint such as c:\psfs\psd15p1. In Windows Explorer, open the Properties for the folder, go to the Mounted Volume properties (this is not the same as the folder security), and set the permission for Administrators/users to Full Control. Use the cacls.exe utility to give the local Administrators group full control and to give Everyone read-only permissions. In the following command, %1 is the mounted folder. cacls %1 /t /m /p Administrators:F Everyone:R For example: cacls c:\psfs\psd1p1 /t /m /p Administrators:F Everyone:R 18 Install SQL Server instances

19 NOTE: If you are installing a retail version of SQL Server, be sure to enter the product key provided with your software. The product key is required for all retail versions of SQL Server. If you do not specify a product key, the installer will add a sample product key ( PID= ABCD ) to the template.ini file. However, MSDN versions of SQL Server already have the product keys embedded in the installation files. Installation considerations for SSAS 2005 instances SSAS 2005 instances are installed through the SQL Server 2005 instance installation procedure (see Install SQL Server 2005 instances on page 27). When you create a template for the installation, select Analysis Services on the Template Features Wizard screen. The SSAS instance will then be installed. SSAS instances can be installed as part of a SQL Server instance installation, or you can install just the SSAS instance. Run the Multi-Node Install Wizard for SQL Server Before starting the wizard, be sure to review the prerequisites and installation considerations described in the SQL Server installation overview on page 13. Also be sure that the product files are in a location that can be accessed by the wizard. Use one of the following procedures to install SQL instances: For SQL Server 2008 instances, see Install SQL Server 2008 Instances, below. For SQL Server 2005 instances, see Install SQL Server 2005 instances on page 27. Install SQL Server 2008 instances To start the Multi-Node Install Wizard for SQL Server, select Tools > Install SQL on the PolyServe Management Console. HP PolyServe Software for Microsoft SQL Server administration guide 19

20 The menu in the left pane of the wizard lists the dialogs included in the installation. You can click on any dialog to open it. When you complete a dialog, the wizard places a checkmark in the box preceding the dialog. On the Welcome window, click Next. Select the Microsoft product to Install dialog Use this dialog to create a new installation product or select an existing installation product. An installation product provides instructions for installing a particular version of SQL Server. The wizard saves the product definition, allowing you to use it again to install additional SQL Server instances of the same version. You can also edit an existing product to change its configuration and can remove a product that is no longer needed. The following example shows a completed dialog. 20 Install SQL Server instances

21 To create a new product, click Add to open the Add Product dialog and then supply the following information. Product Name: Enter a name to identify this product. The name can contain only alphanumeric characters. Product Description: Enter anything you want for the description. Type: The type is always SQL Base Product. Version: Select SQL Media Location: Enter the location of the product files (either a PSFS filesystem or a CIFS share referenced by UNC path, such as \\mynetworkshare\media\sql2008) or click Browse to locate the files. Click Next on the Select the Microsoft product to Install dialog to go to the next dialog. Select the SQL Template File to use dialog A template (INI) file specifies the SQL Server 2008 components to be installed. On this dialog, you can either browse for an existing INI template file or create a new INI template file. HP PolyServe Software for Microsoft SQL Server administration guide 21

22 When you click Create to create a new template file, the Template Feature Wizard appears. This wizard allows you to select the SQL Server components that you want to install. Several features are selected by default, as shown by the checkmarks in the Use column. NOTE: To install a SSAS instance, select Analysis Services. If you are installing only a SSAS instance, be sure that Database Services is not selected. 22 Install SQL Server instances

23 NOTE: The SQL Browser component cannot be edited. The Expand button can be used to see the components in each feature. Add or remove checkmarks to indicate the components that you want to install and then click Save to save the template as an.ini file. The file must be saved in a location that can be accessed by all nodes on which the instance will be installed. Click Next to go to the next dialog. Define the Instances to Install dialog You can define multiple SQL Server 2008 instances and specify the nodes on which each instance should be installed. Instance: Select either Default Instance or Named Instance. Instance Name: If you are installing a default instance, the default instance name MSSQLSERVER will be filled in. If you are installing a named instance, enter the appropriate name for the instance. Instance ID:This ID is used to identify installation directories and registry keys for the instance. By default, the instance name is used as the ID. You can enter a different value if desired. The ID can contain up to 16 alphanumeric characters. The names or IP addresses for the servers in the matrix are listed in the Servers column. To install the instance on all of the servers, click Install on all servers. When you click Install on specific servers, you can select the servers for the instance. NOTE: Do not select nodes that are configured for Virtual MSDTC. The SQL Server installation will fail on these nodes HP PolyServe Software for Microsoft SQL Server administration guide 23

24 When you have completed your selections, click Add and the instances to be created will appear in the table at the bottom of the screen. Repeat this procedure to add other SQL 2008 instances. When you have completed your entries, click Next. Select the Accounts for SQL Instance Administration In SQL Server 2005, the Windows Builtin\Administrator local group was automatically given administrative permissions for the SQL instance. This is no longer the case with SQL Server Instead, when you install an instance, you will need to specify the users and/or groups that should have administrative permissions for the instance. On the following dialog, select the accounts that should have administrative privileges for the SQL instances you are installing. Click Add to open the Select Users or Groups dialog. The User\Group section of the dialog lists the accounts that are specified in the domain controller and belong to the local Administrators group on the nodes selected for the SQL Server installation. Select one or more of those accounts to add them to the Account Name field. (Hold down the Ctrl to select multiple accounts.) When you click Add, the accounts are added to the Accounts dialog. 24 Install SQL Server instances

25 Click Next to continue. FILESTREAM and Hardware Support Options dialog This dialog allows you to enable the FILESTREAM feature on a PSFS share and to install the 32-bit version of SQL Server 2008 on a node with 64-bit hardware. Define File Streaming. The Microsoft FILESTREAM feature is not supported for PSFS filesystems; however you can enable it at your own risk for data stored on a PSFS share. To enable the feature, click Enable FILESTREAM for File I/O Streaming access and then enter a Windows share name such as a CIFS share. HP PolyServe Software for Microsoft SQL Server administration guide 25

26 SQL Server Architecture. If the server has 64-bit hardware but you want to install the 32-bit version of SQL Server 2008, click x86. The FILESTREAM feature cannot be used with the x86 option. It is not supported for 32-bit instances on 64-bit hardware. Click Next to continue. Installation Credentials dialog This dialog asks for the credentials of the user account that will be used to run the installation. After entering your credentials, the wizard will display a list of conditions that must be met for the installation. If these prerequistes are in place on the node, click OK. You will then be asked whether you want to proceed with the installation. When you click Yes, the wizard will start installing the instances. 26 Install SQL Server instances

27 A message on the PolyServe Management Console will report that the operation is in progress. When the operation is complete, a Summary message will report the number of servers that were installed successfully. If the install fails on one or more nodes, the Summary will include a Details button. Click the button for more information about the cause of the failure and also check the log file at: %PROGRAMFILES%\Microsoft SQL Server\100\Setup Bootstrap\LOG Install SQL Server 2005 instances To start the Multi-Node Install Wizard for SQL Server, select Tools > Install SQL on the PolyServe Management Console. HP PolyServe Software for Microsoft SQL Server administration guide 27

28 The menu in the left pane of the wizard lists the dialogs included in the installation. You can click on any dialog to open it. When you complete a dialog, the wizard places a checkmark in the box preceding the dialog. On the Welcome window, click Next. Select the Microsoft product to Install dialog Use this dialog to create a new installation product or select an existing installation product. An installation product provides instructions for installing a particular version of SQL Server. The wizard saves the product definition, allowing you to use it again to install additional SQL Server instances of the same version. You can also edit an existing product to change its configuration and can remove a product that is no longer needed. The following example shows a completed dialog. 28 Install SQL Server instances

29 To create a new product, click Add to open the Add Product dialog and then supply the following information. Product Name: Enter a name to identify this product. The name can contain only alphanumeric characters. Product Description: Enter anything you want for the description. Type: The type is always SQL Base Product. Version: Select SQL Media Location: Enter the location of the product files (either a PSFS filesystem or a CIFS share referenced by UNC path such as \\mynetworkshare\media\sql2005) or click Browse to locate the files. Click Next on the Select the Microsoft product to Install dialog to go to the next dialog. Select the SQL Template File to use dialog A template (INI) file specifies the SQL Server 2005 components to be installed. On this dialog, you can either browse for an existing INI template file or create a new INI template file. HP PolyServe Software for Microsoft SQL Server administration guide 29

30 When you click Create to create a new template file, the Template Feature Wizard appears. This wizard allows you to select the SQL Server components that you want to install. Several features are selected by default, as shown by the checkmarks in the Use column. NOTE: To install a SSAS instance, select Analysis Services. If you are installing only a SSAS instance, be sure that Database Services is not selected. 30 Install SQL Server instances

31 Click Expand to see the components in each feature. Add or remove checkmarks to indicate the components that you want to install and then click Save to save the template as an.ini file. The file must be saved in a location that can be accessed by all nodes on which the instance will be installed. Click Next to go to the next dialog. Installation Credentials dialog This dialog asks for the credentials of the user account that will be used to run the installation. Click Next to go to the next dialog. Define the Instances to Install dialog You can define multiple SQL Server 2005 instances and specify the nodes on which each instance should be installed. HP PolyServe Software for Microsoft SQL Server administration guide 31

32 Instance Name: Enter Default for the default instance, or specify the appropriate name for a named instance. The IP addresses for the servers in the matrix are listed in the Servers column. To install the instance on all of the servers, click Install on all servers. If you click Install on specific servers, you can select the servers for the instance. NOTE: Do not select nodes that are configured for Virtual MSDTC. The SQL Server installation will fail on these nodes. When you have completed your selections, click Add and the instances to be created will appear in the table at the bottom of the screen. Repeat this procedure to add other SQL 2005 instances. When you have completed your entries, click Install. You will then be asked whether you want to proceed with the installation. 32 Install SQL Server instances

33 When you click Yes, the wizard will start installing the instances. A message on the PolyServe Management Console will report that the operation is in progress. When the operation is complete, a Summary message will report the number of servers that were installed successfully. If the install fails on one or more nodes, the Summary will include a Details button. Click the button for more information about the cause of the failure and also check the log file at: %PROGRAMFILES%\Microsoft SQL Server\90\Setup Bootstrap\LOG Other installation tasks Adjust the Maximum Memory setting for SQL Server HP recommends that you reserve approximately 15% of the system resources for the operating system and Matrix Server. For each SQL instance installed, you should change the Maximum Memory default setting for SQL Server from all to 85% (or less) of the total physical RAM on the system. The following script is a template to set the maximum RAM for a particular SQL instance. If multiple instances are installed on the node, you can divide 85% by the number of instances. The exact memory allocation should be studied and defined for your particular environment some instances may require more memory than others. --Set physical memory limit exec sp_configure 'show advanced options',1 reconfigure with override GO int --Set the reserved % create table #tmp([index] int, [Name] sysname, [Internal_Value] int null, HP PolyServe Software for Microsoft SQL Server administration guide 33

34 [Character_Value] sysname null) insert #tmp exec master..xp_msver select from #tmp where [Name]='PhysicalMemory' drop table #tmp exec sp_configure 'max server reconfigure with override GO Requirement for BUILTIN\Administrators group HP PolyServe Software uses Windows authentication (LocalSystem) to connect to SQL Server to make changes. This means that the BUILTIN\Administrators local NT group should be enabled on the primary instance and be part of the SQL Server SysAdmin role. If the BUILTIN\Administrators group must be removed from SQL Server, the following script must be run to explicitly allow LocalSystem account access to SQL Server. -- Giving LocalSystem account access to sqlserver IF NOT EXISTS (SELECT * FROM master.dbo.syslogins WHERE loginname = N'NT Authority\System') EXEC sp_grantlogin N'NT Authority\System' GO -- Set default database EXEC sp_defaultdb N'NT Authority\System', N'master' GO -- Add LocalSystem to SQL SysAdmin group EXEC sp_addsrvrolemember N'NT Authority\System', N'sysadmin' GO --CHECK SYSLOGINS after adding LocalSystem Acct SELECT name FROM master.dbo.syslogins GO TCP/IP Assignments on backup nodes The TCP/IP port selected for a SQL Server installation on a primary node must also be available on the backup nodes for the associated Virtual SQL Server. When you are installing SQL Service on a backup node, verify that no other applications are currently using that port. To see the port assignment for a SQL Server, select Programs > Microsoft SQL Server > Server Network Utility. Then, on the SQL Server Network Utility window, click TCP/IP. The port assignment will then be displayed. You can change the port assignment if necessary. 34 Install SQL Server instances

35 HP PolyServe Software for Microsoft SQL Server administration guide 35

36 36 Install SQL Server instances

37 3 Upgrade SQL Server/SSAS 2005 instances in place This chapter describes how to upgrade SQL Server/SSAS 2005 instances to SQL Server/SSAS 2008 instances. The installation is called in place because the target SQL Server/SSAS 2005 instance is replaced with a SQL Server/SSAS 2008 instance. The old SQL Server/SSAS 2005 data files are automatically converted to the new format. All shared components and instance-specific components are also upgraded. Both virtualized and non-virtualized instances can be upgraded. For virtualized instances, you will need to first place the instance into maintenance mode and then upgrade the instance. After the upgrade, return the instance to operate mode. The monitor/probe will then monitor the upgraded service. The upgrade is performed with the Multi-Node In-Place Upgrade Wizard Prepare for the upgrade Supported upgrades The following instances can be upgraded: MS SQL 2005 x86 SP1 Standard/Enterprise MS SQL 2005 x64 SP1 Standard/Enterprise MS SQL 2005 x86 SP2 Standard/Enterprise MS SQL 2005 x64 SP2 Standard/Enterprise MS SQL 2005 x86 SP3 Standard/Enterprise MS SQL 2005 x64 SP3 Standard/Enterprise MS SQL 2005 x86 Standard/Enterprise MS SQL 2005 x64 Standard/Enterprise Prerequisites SQL Server 2008 prerequisites SQL Server 2008 requires that the following be installed: Windows Installer 4.5 NET Framework 3.5 SP1 SQL Server Native Client SQL Server Setup Support Files Powershell 1.0 HP PolyServe Software for Microsoft SQL Server administration guide 37

38 In-place upgrade prerequisites Before starting the upgrade, complete these steps: Back up all databases that will be upgraded. Prepare databases for the upgrade. Use Microsoft Upgrade Advisor or a similar tool. The Upgrade Advisor analyzes the SQL Server 2005 instances and reports issues that may affect the upgrade. It also provides tips for fixing or working around the issues. Stop PolyServe Instance Aliasing (Open services.msc and stop the service). Start the SQL Browser. If you are using Instance Aliasing, see Configure Instance Aliasing settings on page 108 for information about stopping the PolyServe SQL Browser and starting the SQL Browser. Ensure that the VSQL/VSSAS is running on its primary node and not on any backup node. Place the Virtual SQL/Virtual SSAS instances into maintenance mode. (Select the Virtual SQL Server/Virtual SSAS on the PolyServe Management Console, right-click, and select Maintain.) Restrictions Following are some of the Microsoft restrictions affecting the upgrade. A cross-platform, in-place upgrade from a 32-bit instance of SQL Server 2005 (x86) to a 64-bit instance of SQL Server 2008 (x64) is not supported. The in-place upgrade cannot be used if you want to upgrade only a single database. Upgrading in place is not recommended for certain SQL Server components such as some DTS packages. Also, Notification Services cannot be upgraded in place. When the in-place upgrade process is running, avoid making any changes to the legacy SQL Server 2005 system. All instance-specific components are upgraded; Microsoft does not support having different versions of instance-specific components. For a complete list of the Microsoft restrictions, refer to the SQL Server information on the Microsoft developer network: Run the Multi-Node In-Place Upgrade Wizard Before starting the wizard, be sure to review the prerequisites and restrictions described under Prepare for the upgrade on page 37. Also be sure that the product files are in a location that can be accessed by the wizard. Start the In-Place Upgrade Wizard To start the In-Place Upgrade Wizard, select Tools > In-Place Upgrade SQL on the PolyServe Management Console. The Welcome Screen displays a warning listing information and prerequisites for the upgrade. Verify that the prerequisites are met and then click OK. 38 Upgrade SQL Server/SSAS 2005 instances in place

39 The left pane of the wizard lists the dialogs included in the installation. You can click on any dialog to open it. When you complete a dialog, the wizard places a checkmark in the box preceding the dialog. Click Next on the Welcome Screen to go to the next window. NOTE: You can change your input on the windows at any time. Click Back to return to the appropriate window and then reenter your information. Select the Microsoft product to upgrade dialog Use this dialog to create a new installation product or to select an existing installation product. An installation product provides instructions for installing SQL Server/SSAS instances. The wizard saves the product definition, allowing you to use it again to install additional instances of the same version. You can also edit an existing product to change its configuration and can remove a product that is no longer needed. The following example shows a completed dialog. HP PolyServe Software for Microsoft SQL Server administration guide 39

40 To create a new product, click Add to open the Add Product dialog. Supply the following information on the dialog: Product Name: Enter a unique name to identify this product. The name can contain only alphanumeric characters. Product Description: Enter anything you want for the description. Type: The type is always IPU. Version: The version is always SQL Media Location: Enter the location of the product files (either a PSFS filesystem or a CIFS share referenced by UNC path) or click Browse to locate the files. The Wizard will take care of the correct platform type (upgrading an x86 SQL Server 2K5 instance to an x86 SQL 2K8 instance, and upgrading an x64 SQL Server 2K5 instance to an x64 SQL 2K8 instance). For information about editing or deleting a product, see Add, edit, or delete products on page 46. Click Next on the Select the Microsoft product to Install dialog to go to the next dialog. 40 Upgrade SQL Server/SSAS 2005 instances in place

41 Installation Credentials dialog This dialog asks for the credentials of the user account that will be used to run the installation. The user account must have administrator privileges. After entering the user account information, click Next to go to the next window. Select the Instances to Upgrade dialog Use this dialog to select the instances that you want to upgrade. The dialog lists all SQL Server/SSAS 2005 instances, both virtualized and unvirtualized. Before selecting a virtualized instance, be sure that the Virtual SQL Server/Virtual SSAS is in maintenance mode. The upgrade cannot proceed if the Virtual SQL Server/Virtual SSAS is still in operate mode. HP PolyServe Software for Microsoft SQL Server administration guide 41

42 When you select an instance, all the nodes on which the instance has been installed will be selected. Extending the instance shows details for the instance on each node, including the SQL/OS version and the Virtual SQL Server/Virtual SSAS. The Instance Id can be set or changed by clicking and editing old value in the Instance Id column. When you have completed your selections, click Next. If a Virtual SQL Server/Virtual SSAS for a selected instance has not been placed in maintenance mode, you will see the following error. Click Details to see a list of instances that are not in maintenance mode. Note these instances and then exit from the wizard, place the instances into maintenance mode, and restart the wizard. 42 Upgrade SQL Server/SSAS 2005 instances in place

43 Select Template File dialog A template file records inputs for attributes of certain features being upgraded. On this dialog, you can either browse for an existing template file (and edit it if necessary) or create a new template file. When you click Create to create a new template file, the Template Feature Wizard appears. This wizard allows you to select the features for which you will be supplying attributes. Click Expand to see the components. (The following example has been expanded.) Several features are selected by default, as shown by the checkmarks in the Use column. NOTE: The default values conform to the standard parameter values suggested by Microsoft and can be used for the in-place upgrade. HP PolyServe Software for Microsoft SQL Server administration guide 43

44 Add or remove checkmarks to indicate the components for which you will be providing attributes and enter the necessary values and IDs. When you have completed your entries, click Save to save the template as an.ini file. The template must be saved to a PSFS filesystem or a common share. This file will be used on all of the nodes during the in-place upgrade. NOTE: After the template file has been created, it can be used for subsequent upgrades. If necessary, the file can be modified. Browse to the file on the Select the SQL Template File to use dialog and then click Edit. After making your changes, click Save to save the file to a PSFS filesystem. When you have selected the template file that you want to use for the upgrade, click Upgrade on the Select the SQL Template File to use dialog. 44 Upgrade SQL Server/SSAS 2005 instances in place

45 You will then see the following alert. Click Yes or No as appropriate. Note that the upgrade procedure cannot be reversed. The wizard reports the status of the upgrade, including all nodes participating in the upgrade, the number of remaining operations, and any errors encountered. To run the upgrade in the background, click Background. When the upgrade is complete, a summary message will be displayed. If the upgrade fails on any node, the summary will report that the upgrade failed. The description will list the number of nodes on which the upgrade failed. You will need to correct the issues on those nodes and then restart the upgrade wizard. The SQL upgrade logs are copied to the following directory: %SystemDrive%\Program Files\Polyserve\MatrixServer\conf\debug\SQLLogs Move Virtual SQL Servers/Virtual SSAS to operate mode When the upgrade is complete, you can return the Virtual SQL Servers/Virtual SSAS to operate mode. Select each virtual server on the PolyServe Management Console, right-click, and select Operate. HP PolyServe Software for Microsoft SQL Server administration guide 45

46 If an error occurred on a Virtual SQL Server/Virtual SSAS during the in-place upgrade, the following message will be displayed. A similar error appears for each backup node experiencing a failure. You can either continue with the move to operate mode, or you can exit and launch the In-Place Upgrade Wizard again. IMPORTANT: Be aware that you are proceeding at your own risk if the decision is made to clear the error on each affected node and move to operate mode. Matrix Server does not support this inconsistency. After successfully placing each Virtual SQL Server/Virtual SSAS into operate mode, the corresponding instances will show SQL2008 as the product type on the PolyServe Management Console. Add, edit, or delete products An installation product provides instructions for installing SQL Server/SSAS instances. These products can be created, edited, or deleted on the Select the Microsoft product to upgrade screen. To create a new product, click Add to open the Add Product dialog. 46 Upgrade SQL Server/SSAS 2005 instances in place

47 Supply the following information on the dialog: Product Name: Enter a unique name to identify this product. The name can contain only alphanumeric characters. Product Description: Enter anything you want for the description. Type: The type is always IPU. Version: The version is always SQL Media Location: Enter the location of the product files (either a PSFS filesystem or a CIFS share referenced by UNC path) or click Browse to locate the files. The Wizard will take care of the correct platform type (upgrading an x86 SQL Server 2K5 instance to an x86 SQL 2K8 instance, and upgrading an x64 SQL Server 2K5 instance to an x64 SQL 2K8 instance). To modify an existing product, click Edit on the Select the Microsoft product to upgrade screen. You can then revise the product as necessary. To delete a product, click Remove on the Select the Microsoft product to upgrade screen. A deleted product cannot be recovered. If you want to use the product later on, you will need to recreate it. HP PolyServe Software for Microsoft SQL Server administration guide 47

48 48 Upgrade SQL Server/SSAS 2005 instances in place

49 4 Update SQL Server instances This chapter describes how to install Service Packs and Hotfixes on SQL Server instances. In general, you can install any updates as needed. However, HP prequalifies Service Packs to ensure compatibility with HP PolyServe Software. Check the compatibility matrix on for a list of prequalified Service Packs. Update overview The Multi-Node Update Wizard for SQL Server should be used for all updates of SQL instances that have been virtualized with HP PolyServe Software. The wizard updates both the local profile and the +1 profile on the active node. If the Wizard is not used for an update, version mismatches can occur between the virtual and original registry and the data files on the active node. The Multi-Node Update Wizard can install SQL Server 2005/2008 Service Packs, SSAS 2005/2008 Service Packs, and certain SQL Server hotfixes. Location of service packs and hotfixes The SQL Server product files must be in a location that can be reached by the Multi-Node Update Wizard for SQL Server. The files must be placed in one of these locations: A PSFS filesystem on the SAN storage. A CIFS share referenced by UNC path (the share cannot be specified by a mounted DOS drive letter). An example of a UNC path is \\mynetworkshare\media\sql2008. Maintenance mode is required for update operations Before installing a service pack or hotfix on a virtual SQL or SSAS instance, the Virtual SQL Server (or Virtual SSAS) associated with the instance must be moved to maintenance mode. NOTE: Be sure to put any virtualized SQL or SSAS instances into maintenance mode before attempting to patch the active node. You can patch any passive backup nodes without putting the Virtual SQL or SSAS Server into maintenance mode. For SQL updates, if another Virtual SQL Server (with different instances) is active on the node and is enabled for MSDTC, you will also need to move that Virtual SQL Server to maintenance mode before you install the service pack or hotfix on the instance that you are attempting to patch. If the MSDTC-enabled Virtual SQL Server is not in maintenance mode, the service pack installation will fail. HP PolyServe Software for Microsoft SQL Server administration guide 49

50 Update considerations for SQL Server 2008 Extract zip files Some hotfixes are provided in zip files. Be sure to extract the contacts of the file and review the README before starting the installation. Service pack and hotfix names The installation procedure expects the names of SQL Server service packs and hotfixes to follow the standardized naming schema defined in the following Microsoft Knowledge Base article. The installation will fail if the name of a service pack or hotfix has been changed and it no longer matches the schema. Use of a hidden administrative share During its initialization phase, the SQL Server 2008 setup program uses a hidden administrative share as the location for a tempfolder. If the setup program attempts to place the tempfolder on a PSFS volume where the hidden administrative share is not yet created by LAN Manager, the setup will fail. To work around this problem, use the following command to create an administrative share on the PSFS volume. In the command, s:\ is the PSFS volume. net share s$=s:\ /grant:builtin\administrators,full Update considerations for SQL Server 2005 Instance-Aware components When you perform an unattended installation of SQL Server 2005 SP1 or a SQL Server 2005 hotfix, only instance-aware components (that is, components related to the instance) will be installed. Non-instance-aware components such as SSIS (DTS), Notification Services, and SQL Tools are not updated. This is by Microsoft design. To update the non-instance-aware components, you will need to install SP1 or the hotfix manually and select those components (they are selected by default). This needs to be done only once. You can then perform unattended installations of the service pack or hotfix on your other SQL Server 2005 instances. The non-instance-aware components are installed automatically with SQL Server 2005 SP2. Extract zip files Some hotfixes are provided in zip files. Be sure to extract the contacts of the file and review the README before starting the installation. SQL Server 2005 SP2 required for Full Text Search SQL Server 2005 SP2 is required if you will be using FTE. SP2 provides the NTLM Security Support Provider (NTLMSSP) service, which is used by FTE. Because Windows Server 2008 does not include the NTLMSSP service, FTE will fail if SP2 is not installed. 50 Update SQL Server instances

51 SQL Server 2005 hotfix 2153 Hotfix 2153 for SQL Server 2005 SP1 can be installed via the update wizard; however, the SSIS/NS/Tools components will not be updated. If you need these shared components, update them manually after the wizard has completed. The components will then be registered on the node. NOTE: Instead of installing hotfix 2153, we recommend that you install SP2, which includes the fixes in Hotfix Service pack and hotfix names The installation procedure expects the names of SQL Server service packs and hotfixes to follow the standardized naming schema defined in the following Microsoft Knowledge Base article. The installation will fail if the name of a service pack or hotfix has been changed and it no longer matches the schema. Use of a hidden administrative share During its initialization phase, the SQL Server 2008 setup program uses a hidden administrative share as the location for a tempfolder. If the setup program attempts to place the tempfolder on a PSFS volume where the hidden administrative share is not yet created by LAN Manager, the setup will fail. To work around this problem, use the following command to create an administrative share on the PSFS volume. In the command, s:\ is the PSFS volume. net share s$=s:\ /grant:builtin\administrators,full Installation log files The installation log for SQL Server 2008 Service Packs is located at: %PROGRAMFILES%\Microsoft SQL Server\100\Setup Bootstrap\LOG\Hotfix The installation log for SQL Server 2005 Service Packs is located at: %PROGRAMFILES%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix NOTE: The SQL installation logs are also copied to the following directory: %SystemDrive%\Program Files\Polyserve\MatrixServer\conf\debug\SQLLogs The directory can grow large over time, particularly if the instances are patched regularly. To limit the size of the directory, it should be emptied periodically on all nodes. Run the Multi-Node Update Wizard for SQL Server Be sure to put any virtualized SQL or SSAS instances into maintenance mode before attempting to patch them, as described under Maintenance mode is required for update operations on page 49. HP PolyServe Software for Microsoft SQL Server administration guide 51

52 To start the wizard, select Tools > SP/Hotfix Update SQL on the PolyServe Management Console. The menu in the left pane of the wizard lists the dialogs included in the installation. (The Select Template dialog is not used for SQL Server 2005/2008 updates.) You can click on any dialog to open it. When you complete a dialog, the wizard places a checkmark in the box preceding the dialog. On the Welcome window, click Next. Select the Microsoft product to Update dialog Use this dialog to create a new update product or select an existing update product. An update product provides instructions for installing a particular SQL Server service pack or hotfix. The wizard saves the product definition, allowing you to use it again to update additional SQL Server instances. You can also edit an existing product to change its configuration and can remove a product that is no longer needed. 52 Update SQL Server instances

53 To add a new update product, click Add to open the Add Product dialog. Following is an example for a SQL Server 2008 update. The next example is for a SQL Server 2005 update. Specify the following information on the Add Product dialog. Product Name. Enter a name to identify this product. The name can contain only alphanumeric characters. Product Description. Enter anything you want to identify this update product. HP PolyServe Software for Microsoft SQL Server administration guide 53

54 Type. Select either Service Pack or Hotfix. Version. Select SQL Server 2005 or File Name. Type the name of the service pack or hotfix to be installed or click Browse to locate it. NOTE: Be sure to specify a valid name. If the name is invalid and the operating system does not respond, the wizard will appear to hang. Click Next to go to the next dialog. Installation Credentials dialog This dialog asks for the credentials of the user account that will be used to run the installation. Click Next to go to the next dialog. Select the Instances to Update dialog Select the SQL Server instances that you want to update. NOTE: The dialog lists all of the SQL Server instances on the node, regardless of the SQL Server version. Be sure that the instances you select match the SQL Server product version you specified earlier. 54 Update SQL Server instances

55 To install the update on all of the nodes configured for a particular instance, just click the instance name. If you want to install the update only on certain nodes, expand the instance in the Name/Server column and then check the appropriate nodes. Enter any additional parameters specific to the service pack or hotfix you are installing in the Additional Parameters field. The help for the service pack or hotfix lists the available parameters. For example, if the service pack or hotfix requires that the node be restarted, the help will list a parameter such as /force-restart. The parameters you specify will be run by the Update Wizard. Click Update to begin the update. You will then see a message on the PolyServe Management Console reporting that the operation is in progress. When the operation is complete, an Update Summary message will report the number of servers that were updated successfully. If the update fails on one or more nodes, the Update Summary will include a Details button. Click the button for more information about the cause of the failure and also check the log file. The SQL 2005 log is at: %PROGRAMFILES%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix The SQL 2008 log is at: %PROGRAMFILES%\Microsoft SQL Server\100\Setup Bootstrap\LOG\Hotfix HP PolyServe Software for Microsoft SQL Server administration guide 55

56 56 Update SQL Server instances

57 5 Configure Virtual SQL Servers This chapter describes how to perform the following tasks: Configure Virtual SQL Servers. Assign SQL instances to Virtual SQL Servers. Configure SQL clients. Change the primary node for a Virtual SQL Server. Perform operational tasks such as enabling or disabling a SQL service monitor. Stop SQL Server and Matrix Server. Perform database backups. Configure SQL mail and SQL Agent mail. Uninstall SQL Server instances. Configure Virtual SQL Servers You will need to create Virtual SQL Servers for the SQL instances that you have installed. A Virtual SQL Server includes network interfaces located on a primary node and one or more backup nodes. The SQL instances to be added to the Virtual SQL Server must exist on each of these nodes DNS requirement for Virtual SQL Servers A DNS entry must exist for each Virtual SQL Server/IP address. The entry must include an A record and a PTR record for forward and reverse lookup. Windows authentication may fail if these records do not exist. Be sure to create a DNS entry for each Virtual SQL Server/IP address that you create. Create a Virtual SQL Server To create a Virtual SQL Server, start the PolyServe Management Console and then select Matrix > Add > Add Virtual SQL Server. The Add Virtual SQL Server window appears. HP PolyServe Software for Microsoft SQL Server administration guide 57

58 Virtual IP: Specify the IP address that will be associated with this Virtual SQL Server. Name: Enter the NetBIOS name for this Virtual SQL Server; the name can include up to 15 characters. Application name: An application provides a tag to group Virtual SQL Servers and related virtual SQL instances on the Applications tab. All of the resources associated with the application can then be treated as a unit on the Applications tab. You can specify a new application name, select an existing application name, or leave this field blank. However, if you do not assign a name, Matrix Server will use the IP address for the Virtual SQL Server as the application name. Manage MSDTC: Microsoft Distributed Transaction Coordinator (MS DTC) is used to coordinate transactions between different SQL instances running on different nodes in the cluster. There is one MSDTC service on each machine. NOTE: HP PolyServe Software provides two methods to virtualize MS DTC, thus enabling transactions that span one or more Virtual SQL Servers. MS DTC can be configured for high availability, as described in Chapter 6 on page 77, or it can be managed by a specific Virtual SQL Server. If you will be configuring MS DTC for high availability, do not check Manage MSDTC on the Add Virtual SQL Server dialog. To manage MS DTC via this Virtual SQL Server, HP PolyServe Software and the nodes must be configured as follows: The Manage MSDTC box is checked on the Add Virtual SQL Server dialog. On the nodes configured for the Virtual SQL Server, the Default Coordinator for MSDTC is set to Use local coordinator. This is done on the MSDTC tab of the My Computer Properties dialog (see Appendix B on page 145). If a Remote Host is specified as the Default Coordinator, HP Poly- Serve Software cannot virtualize MSDTC. (Note that if MSDTC is virtualized and the Default Coordinator is then set to a Remote Host, the MSDTC will no longer be managed by the Virtual SQL Server.) The following limitations exist when using a Virtual SQL Server to manage MSDTC. Because only one MSDTC resource exists per machine, you can define MSDTC support for only one Virtual SQL Server per machine. You can, however, define other Virtual SQL Servers that do not support MSDTC. 58 Configure Virtual SQL Servers

59 If two MSDTC-enabled Virtual SQL Servers share the same backup and both Virtual SQL Servers fail, the first server to come up will lock the MSDTC resource, preventing the other Virtual SQL Server from starting. You cannot use COM+ components or MSMQ on a node where MSDTC has been virtualized. Policy: The policy determines the failback action that the Virtual SQL Server will take following a failover to a backup node. AUTOFAILBACK. This policy is intended to return the Virtual SQL Server to its original configuration, or as close to it as possible. After the Virtual SQL Server fails over to a backup node, the ClusterPulse process watches the health of the nodes higher in the list of servers for that Virtual SQL Server. When the health of one of these nodes is equal to or greater than the backup node where the Virtual SQL Server currently resides, the Virtual SQL Server will automatically attempt to fail back to that node. NOFAILBACK. This policy is intended to minimize failovers and is the default. The Virtual SQL Server remains active on the backup node until a healthier node becomes available, at which point the Virtual SQL Server fails over to that node. (On a healthier node, more of the services associated with the Virtual SQL Server will be up than on the node currently hosting the Virtual SQL Server. Up includes the probe statuses UP and Standby.) Network Interfaces Available/Members: Move the interfaces on which the Virtual SQL Server should be configured from the Available column to the Members column. The first interface that you select is the primary interface. The other interfaces that you select are backups. You can use the up and down arrows to reorder the interfaces on the Members column. NOTE: When you modify the configuration of an existing Virtual SQL Server, you can move interfaces between the Available and Members columns, in effect changing the interfaces on which the Virtual SQL Server is configured. However, you cannot move the interface on which the Virtual SQL Server is currently active from the Members column to the Available column. When you click OK, a progress report will display the tasks required to create the Virtual SQL Server. Click Run to start the operation. The new Virtual SQL Server appears on the Servers, Virtual Hosts, and Applications tabs of the PolyServe Management Console. The following example shows two Virtual SQL Servers configured on the servers in the matrix. HP PolyServe Software for Microsoft SQL Server administration guide 59

60 To add a Virtual SQL Server from the command line, use this command: mx vsql add [--policy autofailback nofailback] [--application <application_name>] [--msdtc] [--force yes no] <ip> <name> ([<networkinterface>...]) See the HP PolyServe Matrix Server command reference guide for information about the arguments. Progress reports When you perform operations such as creating a Virtual SQL Server, adding a virtual SQL instance, or moving a Virtual SQL Server to maintenance mode, a progress report is displayed. The report lists the tasks required to perform the operation. Click Run to start the operation. The tasks are checked off as they are performed. If a particular task fails, it is marked with an X and you are asked if you want to continue the operation. The progress report provides two options that can be used if a task fails: Run. Click this button again to retry the failed task. Undo. Click this button to undo all tasks in the list and return the Virtual SQL Server to its original state. You can also cancel the operation at any time by clicking Cancel. When the task currently in progress has completed, HP PolyServe Software will undo each of the completed tasks and the Virtual SQL Server will be returned to its original state. Add a Virtual SQL instance Each Virtual SQL Server can be associated with up to 16 SQL instances. You can add all of the primary SQL instances on a node to the same Virtual SQL Server, or you can create multiple Virtual SQL Servers and spread the primary SQL instances among them. When assigning SQL instances to a Virtual SQL Server, you should be aware of the following: 60 Configure Virtual SQL Servers

61 If you want to use replication on a SQL instance assigned to a Virtual SQL Server, you will need to define the replication after you add the instance to the Virtual SQL Server. If you assign multiple SQL instances to the same Virtual SQL Server, keep in mind that a failure of one instance can cause the Virtual SQL Server to fail over. This failover will include all instances associated with the Virtual SQL Server, not just the failed instance. A Virtual SQL Server can include both SQL Server 2005 and 2008 instances. An instance of SQL Server cannot be virtualized if the physical computer name is changed after the SQL instance is installed and before the instance is virtualized. To add a SQL instance to a Virtual SQL Server, select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Add Virtual SQL Instance. Name: This field lists all of the SQL instances that are available for assignment to this Virtual SQL Server. Select the appropriate SQL instance. NOTE: HP PolyServe Software uses the following rules to determine the SQL instances that can be assigned to the Virtual SQL Server. The Name field does not include instances that do not meet these requirements. The SQL instance must exist on all of the nodes providing network interfaces for the Virtual SQL Server. (The instance must have the same name on all of the nodes.) The SQL instance cannot be in use on any of the nodes as a primary for another Virtual SQL Server. The SQL instance on the primary node cannot currently be a backup for another Virtual SQL Server. Port: Enter the port number for TCP/IP Sockets that the SQL Server instance should listen on. Specifying a port is required. Virtual data root: Specify the full path that will be used for the data files and directories for this virtual SQL Server instance. This location will store the SQL Data Root that was created when the SQL Server instance was installed. (In mx commands, the virtual data root is referred to as the vpath.) HP PolyServe Software for Microsoft SQL Server administration guide 61

62 Master data file, Master log file, Error log file: These fields display the locations of the database and log files. Optional Components: When you add a SQL instance to a Virtual SQL Server, HP PolyServe Software also creates a service monitor. This monitor periodically checks the health of the SQL service for this instance. If the service monitor detects that its check has failed, by default the ClusterPulse process (provided with Matrix Server) will fail over the Virtual SQL Server to a backup node. (You can use the Advanced options to customize this behavior.) NOTE: A failure of the SQL Agent will not trigger a failover of the Virtual SQL Server. When the service monitor detects that the SQL service is down, HP PolyServe Software can try to restart the service instead of immediately failing over the Virtual SQL Server. The optional component SQL Service Restart Attempts allows you to specify the number of attempts that should be made. If you do not specify a number for this component, the Virtual SQL Server will fail over to a backup node. Probe Configuration: The SQL monitor periodically probes the health of the SQL Server service on the node where the Virtual SQL Server is active. The frequency is the interval of time, in seconds, at which the monitor runs the probe. The default setting is 20 seconds. The timeout is the maximum amount of time that will be waited for the probe to complete. The default timeout interval is 15 seconds. NOTE: The probe behavior of the SQL service monitor differs from the default behavior of the service monitors provided with Matrix Server. In Matrix Server, the monitor probes the associated service on all nodes on which it is configured. The SQL monitor probes the SQL service only on the node where the Virtual SQL Server is active. NOTE: A progress window will report each step as the SQL instance is virtualized. The step Virtualize <instance_name> on <node name> as primary may take as long as five minutes to complete. To add a Virtual SQL Instance from the command line, use this command: mx vsqlinstance add <arguments> <vsql\instancename> See the HP PolyServe Matrix Server command reference guide for information about the arguments. View the Virtual SQL instances The PolyServe Management Console shows the complete configuration of the Virtual SQL Server, including the SQL service monitors created for the SQL instances associated with the virtual server. The following example shows the Virtual Hosts tab. 62 Configure Virtual SQL Servers

63 Advanced options for monitors The following information applies to the service monitors that are created with Virtual SQL instances, the Virtual MSDTC Service, and Virtual SSAS instances. NOTE: In this section, virtual host refers to the Virtual SQL Server, Virtual MSDTC, or Virtual SSAS Server associated with the monitor you are configuring. The monitors can be customized for your environment by setting the Advanced options. When you click Advanced on the dialog used to virtualize SQL instances, the MSDTC service, or SSAS instances, you will see two tabs: Policy and Scripts. Policy The Policy tab lets you specify the failover policy and service priority that will apply to the monitor. Timeout and Failure Severity: This setting works with the virtual host policy (either AUTOFAILBACK or NOFAILBACK) to determine what happens when the monitor probe fails. HP PolyServe Software for Microsoft SQL Server administration guide 63

64 The default policies (NOFAILBACK for the virtual host and AUTORECOVER for the monitor) cause the ClusterPulse process to fail over the virtual host to a backup node. The virtual host remains on the backup node until a healthier node becomes available, at which point the virtual host will fail over to that node. You can use the Timeout and Failure Severity attribute to change the failover/failback behavior. There are three settings: NOFAILOVER, AUTORECOVER, and NOAUTORECOVER. NOFAILOVER. When the monitor probe fails, the virtual host does not fail over to a backup node. This option is useful when the monitored resource is not critical, but is important enough that you want to keep a record of its health. To use this option, you must also specify IGNORE as the Event Severity on the Scripts tab. AUTORECOVER. If the virtual host policy is AUTOFAILBACK, when the probe fails, the ClusterPulse process automatically begins failover of the associated virtual host to a backup node. Failback occurs in accordance with the policy setting for the virtual host (either AUTOFAILBACK or NOFAILBACK). NOAUTORECOVER. When the probe fails, the ClusterPulse process automatically begins failover of the associated virtual host to a backup node. The monitor is then disabled on the original node. If the virtual host policy is AUTOFAILBACK, you will need to manually reenable the monitor before failback can occur. This option is useful when integrating HP PolyServe Software with a custom application, where certain application-specific actions must be taken before the failback can occur. Service Priority: The service priority is used when the ClusterPulse process fails over virtual hosts. Service priorities are natural numbers, with 0 (zero) representing the highest priority and higher numbers representing lower priorities. If multiple failures prevent ClusterPulse from placing a virtual host on a node where all of its associated services are available, ClusterPulse next looks for a server where the associated service with the highest priority is available. By default, all service monitors have a priority of 0. Probe Type: The probe type is set to single-probe. A single-probe monitor performs the probe function only on the node where the monitor instance is active. The monitor instance is activated on the node where the associated virtual host is activated, and the probe takes place on that node. The monitor instances on other nodes are marked as standby on the Management Console. If the virtual host fails over to a backup node, the monitor instance on the original node becomes inactive and the probe is no longer run on that node. Matrix Server activates the virtual host on the new node, which causes the monitor instance on that node to change status from standby to active. The monitor then begins probing on that node and the Start script starts the application. If the monitor instance cannot be activated on the new node, the virtual host will fail over to another backup node if possible. Scripts The Scripts tab lets you customize a monitor with Post Start, Post Stop, and Recovery scripts. You can also configure the event severity and script ordering for the monitor. 64 Configure Virtual SQL Servers

65 Script Pathnames: The monitor can optionally be configured with the following types of scripts: Recovery script. Runs after a monitor probe failure is detected, in an attempt to restore the service. Post Start script. Runs after the service has become active on a server. For example, you might want a Post Start script to start a Web server. Pre Stop script. Runs after the service has become inactive on a server. When a monitor is instantiated, the ClusterPulse process chooses the best server to make the service active. The Post Start script is run on this server. On all other servers configured for the monitor, the Pre Stop script is run to ensure that the service is not active. Post Start scripts must be robust enough to run when the service is already started, without considering this to be an error. Similarly, Pre Stop scripts must be robust enough to run when the service is already stopped, without considering this to be an error. In both of these cases, the script should exit with a zero exit status. This behavior is necessary because the Post Start and Pre Stop scripts are run to establish the desired start/stop activity, even though the service may actually have been started by something other than HP PolyServe Software. The Post Start and Pre Stop scripts must also handle recovery from events that may cause them to run unsuccessfully. For example, if the system encounters a problem, the script will fail and exit non-zero. The service could then become active on another node, causing the Pre Stop script to run on the original node even though the Post Start script did not complete successfully. Use custom scripts to modify Start/Stop activities The monitor performs certain starting or stopping activities. If you need to take an action before or after the starting or stopping activity, you can create a custom Start or Stop script for the action and specify it on the Scripts tab for the monitor. The default order for starting is: Run the monitor s starting activities (if any) the custom Start script (if any) HP PolyServe Software for Microsoft SQL Server administration guide 65

66 If you want to reverse this order, preface the Start script with the prefix [pre] on the Scripts tab. The default order for stopping is: Run the custom Stop script (if any) Run the monitor s stopping activities (if any) If you want to reverse this order, preface the Stop script with the prefix [post] on the Scripts tab. Event severity If a PostStart or PostStop script fails or times out, a monitor event is created on the node where the failure or timeout occurred. An event is also created when a monitor probe reports a status of DOWN. (Configuration errors can also cause these events.) You can view the events on the PolyServe Management Console and clear them from the Console after you have fixed the problems that caused them. When an event is created, the ClusterPulse process may initiate failover of the associated virtual host. You can configure the failover behavior with the Event Severity attribute. There are two settings: CONSIDER and IGNORE. CONSIDER. This is the default value. Events are considered when the ClusterPulse process makes failover decisions. IGNORE. Events are ignored; Post Start or Post Stop script failures and DOWN status reports from the monitor will not cause failover. This is useful when the DOWN status or the action performed by the scripts is not critical, but is important enough that you want to keep a record of it. Script ordering Script ordering determines the order in which the Post Start and Post Stop scripts are run when a virtual host moves from one node to another. If you do not configure the monitor with Post Start and Post Stop scripts, the script ordering configuration has no effect. There are two settings: SERIAL and PARALLEL. SERIAL. This is the default setting. When a virtual host moves from one node to another, the following strict ordering sequence for running Post Start and Post Stop scripts is enforced: 1. The Post Stop script is run on all nodes where the virtual server should be inactive. 2. ClusterPulse waits for all Post Stop scripts to complete. 3. The Post Start script on the node where the virtual server is becoming active. PARALLEL. The strict ordering sequence for Post Stop and Post Start scripts is not enforced. The scripts run in parallel across the matrix as a virtual server is in transition. The PARALLEL configuration can speed up failover time for services that do not depend on strict ordering of Post Start and Post Stop scripts. Assuming that it is safe to run the scripts in parallel (which depends on your application), this setting can also increase the chances of a successful failover because ClusterPulse does not have to wait for the failing node to finish running its Stop script. Configure SQL clients To connect to a SQL database on a PSFS filesystem, SQL clients must specify the fully qualified name or the IP address of the Virtual SQL Server, plus the static TCP port number of the SQL instance associated with the SQL database. For example, if VSQL1\Default listens on port 1433 and has the virtual IP address , clients could specify either VSQL1\Default,1433 or , Configure Virtual SQL Servers

67 NOTE: HP PolyServe Software needs to know the port that SQL clients will use to access the SQL database. This means that SQL clients cannot use dynamic port assignment. Certain SQL applications provide their own method to specify this information. If this is not the case for your application, you can create an alias to simplify the amount of information that needs to be entered. You can obtain the information needed for an alias on the HP PolyServe Management Console. To create an alias, use the SQL Server Client Network Utility (C:\winnt\system32\cliconfg.exe). Select the Alias tab and then click Add. You will need to enter the following information on the Add Network Library Configuration window. Server alias: Specify the alias that you want to use for this instance. Network library: Select TCP/IP. Connection parameters: Enter the Virtual SQL Server s fully qualified name or its IP address as the server name. Then uncheck Dynamically determine port and specify the port number associated with the SQL instance. The following example creates the alias mysql for Virtual SQL Server vqar4s6. Port number is assigned to the SQL instance associated with the databases to be accessed. HP PolyServe Software for Microsoft SQL Server administration guide 67

68 A client can then connect to the databases by specifying the server alias on the Connect to SQL Server dialog. Rehost a Virtual SQL Server The Rehost option can be used to change the primary node for a Virtual SQL Server. The Rehost option is available on the HP PolyServe Management Console and can be accessed using either of these methods: On the Applications tab, right-click on the Virtual SQL Server (in the Name column) and then select Rehost. (Or use drag and drop.) On the Servers or Virtual Hosts tab, locate the Virtual SQL Server, right-click, and select Rehost. To change the primary for the Virtual SQL Server, reorder the network interfaces in the Members column. You can also add or remove interfaces from the Virtual SQL Server configuration. NOTE: Check or uncheck Manage msdtc as necessary to allow or disallow virtualization of MSDTC. If MSDTC was previously virtualized under the Virtual SQL Server, Manage msdtc must be checked to continue the virtualization on the new primary node. 68 Configure Virtual SQL Servers

69 After making your changes, click OK. A progress report then appears. The report lists the tasks required to rehost the Virtual SQL Server. Click Run to start the rehost operation. The tasks are checked off as they are performed. When all tasks are completed successfully, the PolyServe Management Console will show the new primary node for the Virtual SQL Server. If a particular task fails, it is marked with an X on the progress report and you are asked if you want to continue the operation. The progress report provides two options that can be used if a task fails: Run. Click this button again to retry the failed task. Undo. Click this button to undo all tasks in the list and return the Virtual SQL Server to its original state. You can also cancel the operation at any time by clicking Cancel. HP PolyServe Software will undo each of the completed steps and return the Virtual SQL Server to its original state. You can also use the following command to rehost a Virtual SQL Server: mx vsql move [--force yes no] [--policy autofailback nofailback] [--application <application_name> [ msdtc] <ip> <name> ([<networkinterface>...]) The --force yes option causes the move to complete even if the operation encounters an error. Be sure to specify the --msdtc option if MSDTC is currently virtualized under the control of the Virtual SQL Server. If this option is omitted, MSDTC will not be virtualized under the Virtual SQL Server. Performance monitoring with perfmon The Windows perfmon utility can be used to collect performance statistics for Virtual SQL/SSAS instances based on the performance counters installed with SQL Server. Virtual SQL/SSAS instances are monitored in the same manner as stand-alone SQL/SSAS instances or instances installed on a MSCS cluster. You must have the appropriate permissions to access the target server (via a physical or virtual hostname). When connected, you can select the desired SQL counters to monitor. Also note the following: Remote Registry Service must be running on the target node. You must have remote registry access right to browse the counter. HP PolyServe Software for Microsoft SQL Server administration guide 69

70 Be sure to use the 64-bit version of perfmon to monitor 64-bit instances. Other SQL Server procedures Maintenance mode When you need to apply a service pack or perform other SQL maintenance, you can move a Virtual SQL Server to maintenance mode. This mode disconnects all clients accessing the SQL instances associated with the Virtual SQL Server. The associated SQL service monitors also stop probing on the primary node. NOTE: If an instance on a backup node is also being used as a backup for a primary instance associated with a different Virtual SQL Server, that instance will no longer have a backup. To minimize the time without a backup, we recommend that you perform the maintenance on the backup instance first and then reenable the SQL service monitor for that instance. The backup instance will then be available for the other primary instance. To move a Virtual SQL Server to maintenance mode, select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Maintain. When you have completed the maintenance activities, you can return the Virtual SQL Server to operation mode. Select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Operate. To place a Virtual SQL Server in maintenance mode from the command line, use this command: mx vsql maintain <vsql> To return the Virtual SQL Server to operation mode, use this command: mx vsql operate <vsql> Create a notifier for the Registry Replicator To assist with monitoring HP PolyServe Software, we recommend that you create a notifier for the alerts generated by the Registry Replicator. (Alerts for the Registry Replicator are in the event range to ) See the HP PolyServe Matrix Server administration guide for information about configuring notifiers. Change the network configuration The SQL Server instance installation captures and stores the current IP network configuration of the node on which it is installed. If you later need to change the network configuration (for example, to remove a NIC or change its IP), it is necessary to devirtualize the Virtual SQL Servers configured on the affected node, make the needed changes, and then revirtualize. To devirtualize a Virtual SQL Server, you will need to delete it from the matrix configuration. Select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Delete. After making your network changes, you can recreate the Virtual SQL Server. 70 Configure Virtual SQL Servers

71 Add a new node to a Virtual SQL Server The new node must be running Matrix Server and HP PolyServe Software and must belong to the matrix. To add the node to a Virtual SQL Server, take these steps: 1. Start the Multi-Node Install Wizard and install the SQL instances associated with the Virtual SQL Server. Use the templates that were used to install the instances on the other nodes configured for the Virtual SQL Server. 2. Add the node to the Virtual SQL Server. Right-click on the Virtual SQL Server, select Properties and then add the node on the Update Virtual SQL Server dialog. Virtual SQL Server procedures Modify the configuration To modify the configuration of a Virtual SQL Server, select it on the PolyServe Management Console window, right-click, and select Properties. You can then change the configuration. NOTE: If MSDTC was previously virtualized under the Virtual SQL Server, be sure to check Manage msdtc on the Update Virtual SQL Server dialog to continue the virtualization on the new primary node. If this option is not checked, MSDTC will not be virtualized. The following restrictions apply: The primary network interface cannot be changed. Additional backup network interfaces can be added; however, the nodes providing the network interfaces must have SQL instances with the same names as the instances associated with the Virtual SQL Server. An instance on the new node cannot currently be the primary for a different Virtual SQL Server; however it can be a backup. To change the configuration from the command line, use this command: mx vsql update [--policy autofailback nofailback] [--application <application_name> [ msdtc] [--force yes no] <ip> <name> ([<networkinterface>...]) The --force yes option causes the update to complete even if the operation encounters an error. Be sure to specify the --msdtc option if MSDTC is currently virtualized under the control of the Virtual SQL Server. If this option is omitted, MSDTC will not be virtualized under the Virtual SQL Server. Virtualize or devirtualize MSDTC When MS DTC is managed by a Virtual SQL Server, you can change the virtualization status of MSDTC at any time. Use one of these methods: Select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Properties. Then check or uncheck Manage MSDTC as needed. Use the mx vsql update command and include or exclude the --msdtc option as appropriate. HP PolyServe Software can virtualize MSDTC only when the Default Coordinator for MSDTC is set to Use local coordinator on the nodes configured for the Virtual SQL Server. If a Remote Host is specified as the Default Coordinator, HP PolyServe Software cannot virtualize MSDTC. HP PolyServe Software for Microsoft SQL Server administration guide 71

72 Enable/disable a Virtual SQL Server A Virtual SQL Server may be left in a disabled state after it is moved via a drag and drop operation. Use the Enable feature to re-enable the Virtual SQL Server. To do this, select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Enable on All Servers. You can also disable a Virtual SQL Server if necessary. Select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Disable on All Servers. To enable or disable a Virtual SQL Server from the command line, use these commands: mx vsql enable <vsql> mx vsql disable <vsql> Delete a Virtual SQL Server To remove a Virtual SQL Server, select it on the PolyServe Management Console, right-click, and select Delete. To delete a Virtual SQL Server from the command line, use this command: mx vsql delete [--force yes no] <vsql> The --force yes option will delete a Virtual SQL Server on a node that is down. View status for a Virtual SQL Server The PolyServe Management Console shows the status of all Virtual SQL Servers configured in the matrix. To view status from the command line, use this command: mx vsql status [--up --down] [--operational --maintenance] [--primary --backup] [--active --inactive] [--showapplication] <vsql> Remove from Server option The Remove from Server option provided on the Management Console should be used only under the direction of PolyServe Technical Support. This option does not perform the necessary clean-up steps. If you need to remove a server from a Virtual SQL Server configuration, use one of these methods while all servers participating in the Virtual SQL Server are up and running: Drag and Drop, the Rehost Virtual SQL Server dialog, or the Virtual SQL Server Properties dialog. Virtual SQL instance procedures Modify the configuration To change the configuration of a SQL instance, select that instance on the PolyServe Management Console, right-click, and select Properties. You can then modify the configuration as necessary. To modify the configuration from the command line, use this command: mx vsqlinstance update <arguments> <vsql\instancename> See the HP PolyServe Matrix Server command reference guide for more information. 72 Configure Virtual SQL Servers

73 Disable or enable a SQL service monitor When a monitor is disabled, the health of the server is affected in the same manner as a failure of the monitor s probe operation. If the Policy configuration of the monitor is either AUTORECOVER or NOAUTORECOVER, the ClusterPulse process will attempt to fail over the Virtual SQL Server to a backup node. If a backup node is not available or if the Policy configuration of the monitor is NOFAILOVER, the Virtual SQL Server will remain active on the original node and the status reported for the monitor will be UP Active (disabled). To disable a SQL service monitor, select it on the PolyServe Management Console, right-click, and select Disable. To reenable the monitor, select it on the Management Console, right-click, and select Enable. Use the following commands to enable or disable the monitor from the command line: mx vsqlinstance enable <vsql\instance> <netif>... mx vsqlinstance disable <vsql\instance> <netif>... Clear monitor errors When a monitor error occurs, the monitor stops operating until the error is cleared. Check the Applications tab for monitor errors (a red E is displayed in the server column associated with the monitor). To clear an error, select the monitor, right-click, and select Clear Last Error. To clear an error from the command line, use this command: mx vsqlinstance clear <vsql\instance> <netif>... Delete a Virtual SQL instance To remove a virtual SQL instance, select that instance on the Management Console, right-click, and select Delete. During the delete, HP PolyServe Software removes the instance from the matrix and performs an operation on the instance to return it to its original state. However, if this operation fails, we recommend that you reinstall the instance. To delete a Virtual SQL Instance from the command line, use this command: mx vsqlinstance delete [ force yes no] <vsql\instance> The --force yes option causes the deletion to take place even when devirtualization fails. Revirtualize a Virtual SQL instance Occasionally you may need to delete a Virtual SQL instance temporarily and restore the instance to its original state. When you recreate the Virtual SQL instance with the Add SQL Instance dialog, a popup message states that the data files for this instance already exist. To reuse these data files with the new Virtual SQL instance, click Revirtualize. If you do not want to use the existing datafiles, click Virtualize. NOTE: The selected virtual path root (or vpath) directory must match the name of the instance being revirtualized. If the names do not match, the instance will not start. HP PolyServe Software for Microsoft SQL Server administration guide 73

74 View status for a Virtual SQL instance The PolyServe Management Console shows the status of all Virtual SQL Instances configured in the matrix. To view status from the command line, use this command: mx vsqlinstance status [arguments] <vsql\instance> The arguments are: [--up --down] [--primary --backup] [--enabled --disabled] [--active --inactive] [--showapplication] With no arguments, the command shows status for all SQL monitors. SQL Agent If the SQL agent fails, a message will appear in the Alert area of the PolyServe Management Console. Failover will not occur. Stop the SQL Service To stop the SQL service on a particular node, first move all Virtual SQL Servers on the node into maintenance mode. You can then use your normal procedure to stop the SQL service. Database backups When you back up the master database directory, be sure to include the following files. HP PolyServe Software requires the files for failover operations. sql.original sql.preg vsql.db Configure SQL Mail and SQL Agent Mail The setup for SQL Mail and/or SQL Agent Mail is the same with or without HP PolyServe Software installed. It is recommended that you use domain authentication, and that the same domain user be configured for each of the following: SQL Server startup account SQL Server Agent startup account MAPI profile See the following Microsoft Knowledge Base articles for more information: Configure Virtual SQL Servers

75 Uninstall SQL Server instances To uninstall a SQL Server instance that has been virtualized with HP PolyServe Software for Microsoft SQL Server, complete these steps: 1. Remove the Virtual SQL instance from each server. (This step also removes the server from the configuration of the Virtual SQL Server associated with the instance.) Start the PolyServe Management Console and then take one of these actions: On the Applications tab, right-click in the cell corresponding to the virtual SQL instance and the server and select Delete. On the Servers or Virtual Hosts tab, right-click on the virtual SQL instance entry for the server and select Delete. Repeat this step on each server on which the Virtual SQL instance is configured. 2. Use the Add/Remove Programs Control Panel Applet to remove the SQL Server instance. NOTE: Do not uninstall instance-unaware components that are shared among multiple instances still running on the server. HP PolyServe Software for Microsoft SQL Server administration guide 75

76 76 Configure Virtual SQL Servers

77 6 Configure Virtual MSDTC The Microsoft Distributed Transaction Coordinator (MS DTC) is the transaction manager responsible for coordinating transaction atomicity across multiple resource managers. It ensures that an update of data (work) is either committed or rolled back on all servers that are participating in the transaction. This chapter describes how to configure MS DTC for high availability. Overview At least two cluster nodes are required to configure MS DTC for high availability. In this configuration, MS DTC is accessed via a virtual host (a Virtual MSDTC). One cluster node is primary for the Virtual MSDTC and the other nodes are backup. An MSDTC Service monitor is associated with the Virtual MSDTC. If the monitor detects that the MS DTC NT service is down or that the MS DTC data path is not available, the Virtual MSDTC can fail over to a backup node, which will continue the MS DTC operations. When configuring nodes to host the Virtual MSDTC, you should be aware of the following: Virtual SQL Servers and Virtual SSAS Servers cannot be hosted on the nodes that are hosting a Virtual MSDTC. The Virtual SQL Servers and Virtual SASS Servers must connect remotely to the Virtual MSDTC service. The Virtual MSDTC nodes must use the same architecture (either 32-bit or 64-bit). The Virtual MSDTC nodes do not need to be dedicated to MS DTC operations and can be used for other activities or applications that do not rely on the local MS DTC service. The Virtual MSDTC nodes can be configured as a separate cluster or they can be included in a larger cluster. The MS DTC transaction logs are stored on a shared PSFS filesystem where they can be accessed by both nodes. DNS requirement for the Virtual MSDTC A DNS entry must exist for the Virtual MSDTC/IP address. The entry must include an A record and a PTR record for forward and reverse lookup. Windows authentication may fail if these records do not exist. DTC transaction statistics When a Virtual MSDTC fails over to another node, the DTC transaction statistics are not carried over to the new node. Instead, the statistics are reset to zero. Create a Virtual MSDTC To create a Virtual MSDTC, start the PolyServe Management Console and then select Matrix > Add > Add Virtual MSDTC. The Add Virtual MSDTC window appears. HP PolyServe Software for Microsoft SQL Server administration guide 77

78 Virtual IP: Specify the IP address that will be associated with this Virtual MSDTC. Virtual MSDTC Name: Enter a name for this Virtual MSDTC; the name must be a valid NetBIOS name and can include up to 15 characters. Application name: An application provides a tag to group Virtual MSDTCs and related virtual MSDTC services on the Applications tab. All of the resources associated with the application can then be treated as a unit on the Applications tab. You can specify a new application name, select an existing application name, or leave this field blank. However, if you do not assign a name, Matrix Server will use the IP address for the Virtual MSDTC as the application name. Policy: The policy determines the failback action that the Virtual MSDTC will take following a failover to a backup node. AUTOFAILBACK. This policy, the default, is intended to return the Virtual MSDTC to its original configuration, or as close to it as possible. After the Virtual MSDTC fails over to a backup node, the ClusterPulse process watches the health of the nodes higher in the list of servers for that Virtual MSDTC. When the health of one of these nodes is equal to or greater than the backup node where the Virtual MSDTC currently resides, the Virtual MSDTC will automatically attempt to fail back to that node. NOFAILBACK. This policy is intended to minimize failovers and is the default. The Virtual MSDTC remains active on the backup node until a healthier node becomes available, at which point the Virtual MSDTC fails over to that node. (On a healthier node, more of the services associated with the Virtual MSDTC will be up than on the node currently hosting the Virtual MSDTC. Up includes the probe statuses UP and Standby.) Network Interfaces Available/Members: The Available column lists the network interfaces that meet the conditions required for the Virtual MSDTC. Move the interfaces on which the Virtual MSDTC should be configured from the Available column to the Members column. The first interface that you select is the primary interface. The other interfaces that you select are backups. You can use the up and down arrows to reorder the interfaces on the Members column. When you click OK, a progress report will display the tasks required to create the Virtual MSDTC. Click Run to start the operation. 78 Configure Virtual MSDTC

79 The new Virtual MSDTC appears on the Servers, Virtual Hosts, and Applications tabs of the PolyServe Management Console. The following Servers tab shows the Virtual MSDTC configuration on a particular node. To add a Virtual MSDTC from the command line, use this command: mx vmsdtc add [--policy autofailback nofailback] [--application <application_name> [--force yes no] <ip> <name> <<network_interface>...> See the HP PolyServe Matrix Server command reference guide for information about the arguments. Progress reports When you perform operations such as creating a Virtual MSDTC or adding a Virtual MSDTC Service, a progress report is displayed. The report lists the tasks required to perform the operation. Click Run to start the operation. The tasks are checked off as they are performed. If a particular task fails, it is marked with an X and you are asked if you want to continue the operation. The progress report provides two options that can be used if a task fails: Run. Click this button again to retry the failed task. Undo. Click this button to undo all tasks in the list and return the Virtual MSDTC to its original state. You can also cancel the operation at any time by clicking Cancel. When the task currently in progress has completed, HP PolyServe Software will undo each of the completed tasks and the Virtual MSDTC will be returned to its original state. HP PolyServe Software for Microsoft SQL Server administration guide 79

80 Add the Virtual MSDTC Service The Virtual MSDTC Service provides a monitor that periodically checks whether the MS DTC NT service is up on the primary node for the Virtual MSDTC and whether the MS DTC data path is accessible from that node. You can add one Virtual MSDTC Service to a Virtual MSDTC. To add the Virtual MSDTC Service, select the Virtual MSDTC on the PolyServe Management Console, right-click, and select Add Virtual MSDTC Service. Virtual data root: Specify a shared PSFS filesystem. The path must be common for all nodes participating in the Virtual MSDTC. (In mx commands, the virtual data root is referred to as the vpath.) Optional Components: When you add a MSDTC Service to a Virtual MSDTC, HP PolyServe Software creates a monitor that watches the MS DTC NT service. When the monitor detects a failure of the NT service, HP PolyServe Software can try to restart the service instead of immediately failing the Virtual MSDTC over to the backup node. The optional component Restart Attempts allows you to specify the number of attempts that should be made. The default is one attempt. Probe Configuration: The frequency is the interval of time, in seconds, at which the monitor runs its probe. The default setting is 20 seconds. The timeout is the maximum amount of time that will be waited for the probe to complete. The default timeout interval is 15 seconds. NOTE: The probe behavior of the MSDTC Service monitor differs from the default behavior of the service monitors provided with Matrix Server. In Matrix Server, the monitor probes the associated service on all nodes on which it is configured. The MSDTC Service monitor probes the MSDTC service only on the node where the Virtual MSDTC is active. The Advanced button on the Add MSDTC Service window displays options that can be used to tailor the monitor for your environment. These options are the same as the advanced options for SQL monitors. See Advanced options for monitors on page 63, for more information. To add a Virtual MSDTC Service from the Command Prompt: mx vmsdtc_service add --vpath <path> [arguments] <vmsdtc\msdtc> See the HP PolyServe Matrix Server command reference guide for information about the arguments. The following view of the Virtual Hosts tab shows the Virtual MSDTC Service configured on a Virtual MSDTC. 80 Configure Virtual MSDTC

81 Actions when configuring the Virtual MSDTC Service When the Virtual MSDTC Service is added, the system temporarily disables the MSDTC on the configured nodes, which causes all inflight MS DTC transactions to be aborted. The following changes are also made on each configured node: MS DTC service is set to manual. The MS DTC log is set to point to the shared location on the PSFS filesystem (the virtual data root). Network DTC Access is enabled. 1. Open Component Services by selecting Start > Programs > Administrative Tools. 2. Expand the Component Services folder and browse to the My Computer folder. 3. Expand the My Computer folder to see the Distributed Transaction Coordinator folder and then the Local DTC folder. 4. Right-click Local DTC to open its properties dialog, which shows the following Security dialog. HP PolyServe Software for Microsoft SQL Server administration guide 81

82 Configure other nodes for Virtual MSDTC To use the high-availability MSDTC service, the cluster nodes running Virtual SQL Servers or Virtual SSAS Servers must be configured to access the Virtual MSDTC. Complete the following steps on each node: 1. Open Component Services by selecting Start > Programs > Administrative Tools. 2. Expand the Component Services folder and browse to the My Computer folder. 3. Right click on My Computer to bring up its properties dialog and then select the MSDTC tab. 4. Ensure that Use local coordinator is unchecked and, at the Remote coordinator host name prompt, specify the Virtual MSDTC. 82 Configure Virtual MSDTC

83 Rehost a Virtual MSDTC The Rehost option can be used to change the primary node for a Virtual MSDTC. You can use drag and drop on the Applications tab to move the Virtual MSDTC from the current primary node to another node, or you can select the Rehost option using either of these methods: On the Applications tab, right-click on the Virtual MSDTC (in the Name column) and then select Rehost. (Or use drag and drop.) On the Servers or Virtual Hosts tab, locate the Virtual MSDTC, right-click, and select Rehost. When the Rehost option is selected, the following dialog appears. HP PolyServe Software for Microsoft SQL Server administration guide 83

84 To change the primary for the Virtual MSDTC, reorder the network interfaces in the Members column. You can also add or remove interfaces from the Virtual MSDTC configuration. After making your changes, click OK. After completing the Rehost Virtual MSDTC dialog or using drag and drop to move the Virtual MSDTC, you will see a progress report listing the tasks required to rehost the Virtual MSDTC. Click Run on the progress report to start the rehost operation. The tasks are checked off as they are performed. When all tasks are completed successfully, the PolyServe Management Console will show the new primary node for the Virtual MSDTC. If a particular task fails, it is marked with an X on the progress report and you are asked if you want to continue the operation. The progress report provides two options that can be used if a task fails: Run. Click this button again to retry the failed task. Undo. Click this button to undo all tasks in the list and return the Virtual MSDTC to its original state. You can cancel the operation at any time by clicking Cancel. HP PolyServe Software will undo each of the completed steps and return the Virtual MSDTC to its original state. NOTE: A Virtual MSDTC may be left in a disabled state after it is moved via a drag and drop operation. To re-enable the Virtual MSDTC, select the Virtual MSDTC on the PolyServe Management Console, right-click, and select Enable on All Servers. To rehost a Virtual MSDTC from the command line, use this command: mx vmsdtc move [--policy autofailback nofailback] [--application <application_name> [--force yes no] <ip> <name> <<network_interface>...> The --force yes option causes the move to complete even if the operation encounters an error. 84 Configure Virtual MSDTC

85 Other Virtual MSDTC procedures Add a new node to a Virtual MSDTC The new node must be running Matrix Server and HP PolyServe Software for Microsoft SQL Server and must belong to the same cluster as the Virtual MSDTC nodes. The new node cannot belong to a Virtual SQL Server or Virtual SSAS. To add the node to the Virtual MSDTC, right-click the Virtual MSDTC, select Properties, and then add the node on the Update Virtual MSDTC dialog. Virtual MSDTC procedures Modify the configuration To modify the configuration of a Virtual MSDTC, select it on the PolyServe Management Console window, right-click, and select Properties. You can then change the configuration. NOTE: When you modify the configuration of an existing Virtual MSDTC, you can move interfaces between the Available and Members columns, in effect changing the interfaces on which the Virtual MSDTC is configured. However, you cannot move the interface on which the Virtual MSDTC is currently active from the Members column to the Available column. To change the configuration from the command line, use this command: mx vmsdtc update [--policy nofailback autofailback] [--application <application_name> [--force yes no] <ip> <name> <<network_interface>...> Enable/disable a Virtual MSDTC A Virtual MSDTC may be left in a disabled state after it is moved via a drag and drop operation. Use the Enable feature to re-enable the Virtual MSDTC. To do this, select the Virtual MSDTC on the PolyServe Management Console, right-click, and select Enable on All Servers. You can also disable a Virtual MSDTC if necessary. select the Virtual MSDTC on the PolyServe Management Console, right-click, and select Disable on All Servers. To enable or disable a Virtual MSDTC from the command line, use these commands: mx vmsdtc enable <vmsdtc> mx vmsdtc disable <vmsdtc> Delete a Virtual MSDTC To remove a Virtual MSDTC, select it on the PolyServe Management Console, right-click, and select Delete. To delete a Virtual MSDTC from the command line, use this command: mx vmsdtc delete [--force yes no] <vmsdtc> HP PolyServe Software for Microsoft SQL Server administration guide 85

86 View status for a Virtual MSDTC The PolyServe Management Console shows the status of all Virtual MSDTCs configured in the matrix. To view status from the command line, use this command: mx vmsdtc status [--up --down] [--operational --maintenance] [--primary --backup] [--active --inactive] [--showapplication] <vmsdtc> Virtual MSDTC Service procedures Modify the configuration To change the configuration of the Virtual MSDTC Service, select it on the PolyServe Management Console, right-click, and select Properties. You can then modify the configuration as necessary. To modify the configuration from the command line, use this command: vmsdtc_service update <arguments> <ip> <name> <<network_interface>...> The arguments are the same as vmsdtc_service add, with the exception that the --vpath argument does not apply. See the HP PolyServe Matrix Server command reference guide for more information about the arguments. Disable or enable a Virtual MSDTC Service When a monitor is disabled, the health of the server is affected in the same manner as a failure of the monitor s probe operation. If the Policy configuration of the monitor is either AUTORECOVER or NOAUTORECOVER, the ClusterPulse process will attempt to fail over the Virtual MSDTC to a backup node. If a backup node is not available or if the Policy configuration of the monitor is NOFAILOVER, the Virtual MSDTC will remain active on the original node and the status reported for the monitor will be UP Active (disabled). To disable a Virtual MSDTC Service monitor, select it on the PolyServe Management Console, right-click, and select Disable. To reenable the monitor, select it on the Management Console, right-click, and select Enable. Use the following commands to enable or disable the monitor from the command line: vmsdtc_service enable <vmsdtc\msdtc> <netif>... vmsdtc_service disable <vmsdtc\msdtc> <netif>... Remove a Virtual MSDTC Service To remove a virtual MSDTC service, select the service on the Management Console, right-click, and select Delete. To remove the service from the command line, use this command: vmsdtc_service delete [ force yes no] <vmsdtc\msdtc> Remove a server from the Virtual MSDTC Service To remove a server from the configuration of the Virtual MSDTC Service, select the Virtual MSDTC Server on the PolyServe Management Console, right-click, and select Remove From Server. 86 Configure Virtual MSDTC

87 View Alerts for the Virtual MSDTC Service To view any current Alert messages, select the Virtual MSDTC Server on the PolyServe Management Console, right-click, and select View Alerts. Clear a monitor error for the Virtual MSDTC Service When a monitor error occurs, the monitor stops operating until the error is cleared. Check the Applications tab for monitor errors (a red E is displayed in the server column associated with the monitor). To clear the error, select the monitor, right-click, and select Clear Last Error. To clear an error from the command line, use this command: mx vmsdtc_service clear <vmsdtc\msdtc> <netif>... View status for the Virtual MSDTC Service The PolyServe Management Console shows the status of the Virtual MSDTC Service. To view status from the command line, use this command: mx vmsdtc_service status [arguments] The arguments are: [--up --down] [--primary --backup] [--enabled --disabled] [--active --inactive] [--showapplication] HP PolyServe Software for Microsoft SQL Server administration guide 87

88 88 Configure Virtual MSDTC

89 7 Configure SQL Server Analysis Services Microsoft SQL Server Analysis Services (SSAS) provides online analytical processing (OLAP) and data mining features. This chapter describes how to configure SSAS for high availability. Overview Two or more cluster nodes are required to configure SSAS for high availability. In this configuration, SSAS is accessed via a virtual host (a Virtual SSAS). One cluster node is primary for the Virtual SSAS and the other nodes are backups. A Virtual SSAS instance and Analysis Services Service monitor is associated with the Virtual SSAS. If the monitor detects that the SSAS NT service is down or that the SSAS data path is not available, the Virtual SSAS can fail over to a backup node, which will continue the SSAS operations. Configure a Virtual SSAS You will need to create a separate Virtual SSAS for each SQL SSAS instance that you have installed. A Virtual SSAS includes network interfaces located on a primary node and one or more backup nodes. The SSAS instance to be added to the Virtual SASS must exist on each of these nodes. DNS requirement for Virtual SSAS A DNS entry must exist for each Virtual SSAS/IP address. The entry must include an A record and a PTR record for forward and reverse lookup. Windows authentication may fail if these records do not exist. Be sure to create a DNS entry for each Virtual SSAS Server/IP address that you create. Create a Virtual SSAS To create a Virtual SSAS, start the PolyServe Management Console and then select Matrix > Add > Add Virtual Analysis Services. The Add Virtual Analysis Services window appears. HP PolyServe Software for Microsoft SQL Server administration guide 89

90 Virtual IP: Specify the IP address that will be associated with this Virtual SSAS. Name: Enter the NetBIOS name for this Virtual SSAS. The name can include up to 15 characters. Application name: An application provides a tag to group Virtual SSASs and related virtual SSAS instances on the Applications tab. All of the resources associated with the application can then be treated as a unit on the Applications tab. You can specify a new application name (maximum of 32 characters), select an existing application name, or leave this field blank. However, if you do not assign a name, Matrix Server will use the IP address for the Virtual SSAS as the application name. Policy: The policy determines the failback action that the Virtual SSAS will take following a failover to a backup node. AUTOFAILBACK. This policy is intended to return the Virtual SSAS to its original configuration, or as close to it as possible. After the Virtual SSAS fails over to a backup node, the ClusterPulse process watches the health of the nodes higher in the list of servers for that Virtual SSAS. When the health of one of these nodes is equal to or greater than the backup node where the Virtual SSAS currently resides, the Virtual SSAS will automatically attempt to fail back to that node. NOFAILBACK. This policy is intended to minimize failovers and is the default. The Virtual SSAS remains active on the backup node until a healthier node becomes available, at which point the Virtual SSAS fails over to that node. (On a healthier node, more of the services associated with the Virtual SSAS will be up than on the node currently hosting the Virtual SSAS. Up includes the probe statuses UP and Standby.) Network Interfaces Available/Members: Move the interfaces on which the Virtual SSAS should be configured from the Available column to the Members column. The first interface that you select is the primary interface. The other interfaces that you select are backups. You can use the up and down arrows to reorder the interfaces on the Members column. When you click OK, a progress report will display the tasks required to create the Virtual SSAS. Click Run to start the operation.the new Virtual SSAS appears on the Servers, Virtual Hosts, and Applications tabs of the PolyServe Management Console. The following example shows a Virtual SSAS configured on two nodes of the matrix. 90 Configure SQL Server Analysis Services

91 To add a Virtual SSAS from the command line, use this command: mx vssas add [--policy autofailback nofailback] [--application <application_name> [--force yes no] <ip> <name> ([<networkinterface>...]) See the HP PolyServe Matrix Server command reference guide for information about the arguments. Progress reports When you perform operations such as creating a Virtual SSAS, adding a virtual SSAS instance, or moving a Virtual SSAS to maintenance mode, a progress report is displayed. The report lists the tasks required to perform the operation. Click Run to start the operation. The tasks are checked off as they are performed. If a particular task fails, it is marked with an X and you are asked if you want to continue the operation. The progress report provides two options that can be used if a task fails: Run. Click this button again to retry the failed task. Undo. Click this button to undo all tasks in the list and return the Virtual SASS to its original state. You can also cancel the operation at any time by clicking Cancel. When the task currently in progress has completed, HP PolyServe Software will undo each of the completed tasks and the Virtual SSAS will be returned to its original state. HP PolyServe Software for Microsoft SQL Server administration guide 91

92 Add a Virtual SSAS instance Each Virtual SSAS can be associated with one SSAS instance. When assigning a SSAS instance to a Virtual SSAS, you should be aware of the following: The Virtual SSAS must be active on its primary node and cannot be in maintenance mode. To add a SSAS instance to a Virtual SSAS select the Virtual SSAS on the PolyServe Management Console, right-click, and select Add Analysis Services Service. Name: This field lists all of the SSAS instances that are available for assignment to this Virtual SSAS. Select the appropriate SSAS instance. NOTE: HP PolyServe Software uses the following rules to determine the SSAS instances that can be assigned to the Virtual SSAS. The Name field does not include instances that do not meet these requirements. The SSAS instance must exist on all of the nodes providing network interfaces for the Virtual SSAS. (The instance must have the same name on all of the nodes.) The SSAS instance cannot be in use on any of the nodes as a primary for another Virtual SSAS. SSAS instance on the primary node cannot currently be a backup for another Virtual SSAS. Virtual data root: Specify the full path for the PSFS filesystem that will be used for the data files and directories for this SSAS instance. (In mx commands, the virtual data root is referred to as the vpath.) Data path, Log path: These fields display the locations of the SSAS data and log files. Optional Components: When you add a SSAS instance to a Virtual SSAS, HP PolyServe Software creates a monitor that periodically checks whether the Analysis Services NT service is up and whether the data path on the shared PSFS filesystem is accessible on the node hosting the Virtual SSAS. When the monitor detects a failure of the NT service, HP PolyServe Software can try to restart the service instead of immediately failing the Virtual SSAS over to the backup node. The optional component Restart Attempts allows you to specify the number of attempts that should be made. The default is one attempt. 92 Configure SQL Server Analysis Services

93 Probe Configuration: The frequency is the interval of time, in seconds, at which the monitor runs its probe. The default setting is 20 seconds. The timeout is the maximum amount of time that will be waited for the probe to complete. The default timeout interval is 15 seconds. NOTE: The probe behavior of the Virtual SSAS instance monitor differs from the default behavior of the service monitors provided with Matrix Server. In Matrix Server, the monitor probes the associated service on all nodes on which it is configured. The Analysis Services Service monitor probes the Analysis Services service only on the node where the Virtual SSAS is active. The Advanced button on the Add Analysis Services Service window displays options that can be used to tailor the monitor for your environment. These options are the same as the advanced options for SQL monitors. See Advanced options for monitors on page 63, for more information. To add a SSAS instance from the Command Prompt: mx vssasinstance add --vpath <path> [arguments] <vssas\ssas_instance> See the HP PolyServe Matrix Server command reference guide for information about the arguments. The following screen shows a Virtual SSAS instance configured on a Virtual SSAS. HP PolyServe Software for Microsoft SQL Server administration guide 93

94 Monitoring Virtual SSAS instances SQL Server Profiler When you start a new trace with SQL Server Profiler, you are prompted for the server name. The browse feature associated with the server name prompt cannot locate Virtual SSAS named or default instances. Instead, enter the name of the Virtual SSAS instance as the server name. Surface Area Configuration tool To use the Surface Area Configuration tool with a Virtual SSAS instance, you will need to connect to the Virtual SSAS instead of to the server on which you are running the tool. To connect to the Virtual SSAS, open the Surface Area Configuration Tool and, at the Configure Surface Area for localhost heading, click changecomputer. On the Select Computer dialog, click Remote computer and specify the IP address of the Virtual SSAS. The SQL Server Surface Area Configuration window now specifies the Virtual SSAS instead of the localhost and you can use the tool to manage SSAS instances associated with the Virtual SSAS. 94 Configure SQL Server Analysis Services

95 Performance monitoring with perfmon The Windows perfmon utility can be used to collect performance statistics for Virtual SSAS instances based on the performance counters installed with SQL Server. Virtual SSAS instances are monitored in the same manner as stand-alone SSAS instances or instances installed on a MSCS cluster. You must have the appropriate permissions to access the target server (via a physical or virtual hostname). When connected, you can select the desired counters to monitor. Also note the following: Remote Registry Service must be running on the target node. You must have remote registry access right to browse the counter. Be sure to use the 64-bit version of perfmon to monitor 64-bit instances. Rehost a Virtual SSAS The Rehost option can be used to change the primary node for a Virtual SSAS. You can use drag and drop on the Applications tab to move the Virtual SSAS from the current primary node to another node, or you can select the Rehost option using either of these methods: On the Applications tab, right-click the Virtual SSAS (in the Name column) and then select Rehost. (Or use drag and drop.) On the Servers or Virtual Hosts tab, locate the Virtual SSAS, right-click, and select Rehost. When the Rehost option is selected, the following dialog appears: HP PolyServe Software for Microsoft SQL Server administration guide 95

96 To change the primary for the Virtual SSAS, reorder the network interfaces in the Members column. You can also add or remove interfaces from the Virtual SSAS configuration. After making the changes, click OK. After completing the Rehost Virtual Analysis Services dialog or using drag and drop to move the Virtual SSAS, you will see a progress report listing the tasks required to rehost the Virtual SSAS. Click Run on the progress report to start the rehost operation. The tasks are checked off as they are performed. When all tasks are completed successfully, the PolyServe Management Console will show the new primary node for the Virtual SSAS. If a particular task fails, it is marked with an X on the progress report and you are asked if you want to continue the operation. The progress report provides two options that can be used if a task fails: Run. Click this button again to retry the failed task. Undo. Click this button to undo all tasks in the list and return the Virtual SSAS to its original state. 96 Configure SQL Server Analysis Services

97 You can cancel the operation at any time by clicking Cancel. HP PolyServe Software will undo each of the completed steps and return the Virtual SSAS to its original state. NOTE: A Virtual SSAS may be left in a disabled state after it is moved via a drag and drop operation. To re-enable the Virtual SSAS, select the Virtual SSAS on the PolyServe Management Console, right-click, and select Enable on All Servers. To rehost a Virtual SSAS from the command line, use this command: mx vssas move [--policy autofailback nofailback] [--application <application_name>][--force yes no] <ip> <name> ([<networkinterface>...]) The --force yes option causes the move to complete even if the operation encounters an error. Other Virtual SSAS procedures Maintenance mode When you need to apply a service pack or perform other SSAS maintenance, you can move a Virtual SSAS to maintenance mode. This mode disconnects all clients accessing the SSAS instances associated with the Virtual SSAS. The associated SSAS service monitors also stop probing on the primary node. NOTE: If an instance on a backup node is also being used as a backup for a primary instance associated with a different Virtual SSAS, that instance will no longer have a backup. To minimize the time without a backup, we recommend that you perform the maintenance on the backup instance first and then reenable the SSAS service monitor for that instance. The backup instance will then be available for the other primary instance. To move a Virtual SSAS to maintenance mode, select the Virtual SSAS on the PolyServe Management Console, right-click, and select Maintain. When you have completed the maintenance activities, you can return the Virtual SSAS to operation mode. Select the VSSAS on the PolyServe Management Console, right-click, and select Operate. To place a VSSAS in maintenance mode from the command line, use this command: mx vssas maintain <vssas> To return the Virtual SQL Server to operation mode, use this command: mx vssas operate <vssas> Add a new node to a Virtual SSAS The new node must be running Matrix Server and HP PolyServe Software and must belong to the same cluster as the nodes configured for the Virtual SSAS. To add the node to a Virtual SSAS, right-click on the Virtual SSAS, select Properties, and then add the node on the Update Virtual Analysis dialog. HP PolyServe Software for Microsoft SQL Server administration guide 97

98 Virtual SSAS procedures Modify the configuration To modify the configuration of a Virtual SSAS, select it on the PolyServe Management Console window, right-click, and select Properties. You can then change the configuration, with the exception that the primary interface cannot be changed. NOTE: When you modify the configuration of a Virtual SSAS, you can move interfaces between the Available and Members columns, in effect changing the interfaces on which the Virtual SSAS is configured. However, you cannot move the interface on which the Virtual SSAS is currently active from the Members column to the Available column. To change the configuration from the command line, use this command: mx vssas update [--policy autofailback nofailback] [--application <application_name> [--force yes no] <ip> <name> <<networkinterface>...> The --force yes option causes the update to complete even if the operation encounters an error. Enable/disable a Virtual SSAS A Virtual SSAS may be left in a disabled state after it is moved via a drag and drop operation. Use the Enable feature to re-enable the Virtual SSAS. To do this, select the Virtual SSAS on the PolyServe Management Console, right-click, and select Enable on All Servers. You can also disable a Virtual SQL Server if necessary. select the Virtual SSAS on the PolyServe Management Console, right-click, and select Disable on All Servers. To enable or disable a Virtual SSAS from the command line, use these commands: mx vssas enable <vssas> mx vssas disable <vssas> Delete a Virtual SSAS To remove a Virtual SSAS, select it on the PolyServe Management Console, right-click, and select Delete. To delete a Virtual SSAS from the command line, use this command: mx vssas delete [--force yes no] <vssas> View status for a Virtual SSAS The PolyServe Management Console shows the status of all Virtual SSASs configured in the matrix. To view status from the command line, use this command: mx vssas status [--up --down] [--enabled --disabled] [--operational --maintenance] [--primary --backup] [--active --inactive] [--showapplication] <vssas> 98 Configure SQL Server Analysis Services

99 Virtual SSAS instance procedures Modify the configuration To change the configuration of a Virtual SSAS instance, select that instance on the PolyServe Management Console, right-click, and select Properties. You can then modify the configuration as necessary. To modify the configuration from the command line, use this command: mx vssasinstance update <arguments> <vssas\instancename> The arguments are the same as vssasinstance add, with the exception that the --vpath argument does not apply. See the HP PolyServe Matrix Server command reference guide for more information. Disable or enable a Virtual SSAS instance When a monitor is disabled, the health of the server is affected in the same manner as a failure of the monitor s probe operation. If the Policy configuration of the monitor is either AUTORECOVER or NOAUTORECOVER, the ClusterPulse process will attempt to fail over the Virtual SSAS to a backup node. If a backup node is not available or if the Policy configuration of the monitor is NOFAILOVER, the Virtual SSAS will remain active on the original node and the status reported for the monitor will be UP Active (disabled). To disable a Virtual SSAS instance monitor, select it on the PolyServe Management Console, right-click, and select Disable. To reenable the monitor, select it on the Management Console, right-click, and select Enable. Use the following commands to enable or disable the monitor from the command line: mx vssasinstance enable <vssas\instance> <netif> mx vssasinstance disable <vssas\instance> <netif> Clear monitor errors When a monitor error occurs, the monitor stops operating until the error is cleared. Check the Applications tab for monitor errors (a red E is displayed in the server column associated with the monitor). To clear an error, select the monitor, right-click, and select Clear Last Error. To clear an error from the command line, use this command: mx vssasinstance clear <vssas\instance> <netif>... Delete a Virtual SSAS instance To remove a Virtual SSAS instance, select that instance on the Management Console, right-click, and select Delete. During the delete, HP PolyServe Software removes the instance from the matrix and performs an operation on the instance to return it to its original state. However, if this operation fails, we recommend that you reinstall the instance. To delete a Virtual SSAS instance from the command line, use this command: mx vssasinstance delete [ force yes no] <vssas\instance> The --force yes option causes the deletion to take place even when devirtualization fails. HP PolyServe Software for Microsoft SQL Server administration guide 99

100 Revirtualize a Virtual SSAS instance Occasionally you may need to delete a Virtual SSAS Instance temporarily and restore the instance to its original state. When you recreate the Virtual SSAS Instance with the Add IAnalysis Services Service dialog, a popup message states that the data files for this instance already exist. To reuse these data files with the new Virtual SSAS Instance, click Revirtualize. If you do not want to use the existing datafiles, click Virtualize. NOTE: The selected virtual path root (or vpath) directory must match the name of the instance being revirtualized. If the names do not match, the instance will not start. View status for a Virtual SSAS instance The PolyServe Management Console shows the status of the Virtual SSAS instances. To view status from the command line, use this command: mx vssasinstance status [arguments] <vssas\instance> The arguments are: [--up --down] [--primary --backup] [--enabled --disabled] [--active --inactive] [--showapplication] With no arguments, the command shows status for all Virtual SSAS instances. 100 Configure SQL Server Analysis Services

101 8 Using the Applications tab Overview The Applications tab on the PolyServe Management Console shows all SQL Server resources (Virtual SQL Servers and virtual SQL instances, Virtual MSDTC and Virtual MSDTC Service, Virtual SSAS and virtual SSAS instances) configured in the matrix and enables you to manage and monitor them from a single screen. The SQL Server resources are grouped under the applications that you specified when you created the resources. The applications and resources appear in the rows of the table. (Double-click on a resource to see its properties.) Each application can be treated as a unit. Using the Applications tab, you can quickly determine whether clients are able to access the applications. If a problem occurs, you can drill-down the affected application to locate the resource experiencing the problem. For more information about the Applications tab, see Using the Applications Tab in the HP PolyServe Matrix Server administration guide. SQL resources on the Application tab Virtual SQL Servers and Virtual SQL instances The Applications tab shows all of the Virtual SQL Servers and virtual SQL instances configured in the matrix. The Application names assigned to the Virtual SQL Servers are listed in the Name column. When you click on an application, you will see the Virtual SQL Servers associated with that application, as well as the virtual SQL instances assigned to those Virtual SQL Servers. HP PolyServe Software for Microsoft SQL Server administration guide 101

102 The columns show the configuration of each Virtual SQL Server. A P indicates the primary server; a number indicates that the server is a backup. The green checkmark specifies the server on which the Virtual SQL Server is currently active. You can use the Status column to locate any problems in the matrix. Everything is okay in this matrix. Virtual MSDTC and Virtual MSDTC Service The Applications tab shows the configuration of the Virtual MSDTC and Virtual MSDTC Service. To display the configuration, click, in the Name column, on the application name assigned to the Virtual MSDTC. In this example, the Virtual MSDTC is configured on two servers: qars9 and qars10. In the server columns, the P indicates the primary server for the Virtual MSDTC; a number indicates that the server is a backup. The green checkmark specifies the server on which the Virtual MSDTC is currently active. You can use the Status column to locate any problems in the matrix. Everything is okay in this matrix. 102 Using the Applications tab

103 Virtual SSAS and Virtual SSAS instances The Applications tab shows the configuration of the Virtual SSAS and Virtual SSAS instances. To display the configuration, click, in the Name column, on the application name assigned to the Virtual SSAS. In this example, the Virtual SSAS is configured on two servers. HP PolyServe Software for Microsoft SQL Server administration guide 103

104 In the server columns, the P indicates the primary server for the Virtual SSAS; a number indicates that the server is a backup. The green checkmark specifies the server on which the Virtual SSAS is currently active. You can use the Status column to locate any problems in the matrix. Everything is okay in this matrix. Monitor errors When a monitor error occurs, the monitor stops operating until the error is cleared. The Applications tab displays a red E for a monitor that is experiencing an error. In the following example for a virtual SQL instance monitor, the monitor error is on the primary server, tmr11s410. To clear the error, right-click in the server cell for the monitor and select Clear last error. 104 Using the Applications tab

105 Manage the SQL configuration The Applications tab provides two ways to manage the SQL configuration. You can use drag and drop to make changes, or you can right-click on an object and then select the appropriate menu item. Drag and drop Drag and drop operations for Virtual SQL Servers, virtual SQL instances, Virtual SSAS Servers, virtual SSAS instances, Virtual MSDTC, and the Virtual MSDTC Service work in the same manner as Matrix Server virtual hosts and monitors. See the HP PolyServe Matrix Server administration guide for more information. NOTE: Moving a Virtual SQL Server via drag and drop may leave the Virtual SQL Server is a disabled state. Right-click on the Virtual SQL Server and select Enable on all servers to re-enable it. Caution when using drag and drop When moving a Virtual SQL Server via drag and drop, be sure to avoid creating a situation in which a Virtual SQL Server cannot fail over because its only backup node is the primary for another Virtual SQL Server providing an instance with the same name. In the following simple example, Virtual SQL Server VSQL1 is providing Instance1, with the primary on node1 and the backup on node2. Virtual SQL Server VSQL2 is also providing an Instance1, with the primary on node3 and the backup on node 2. The Virtual SQL Servers are sharing a backup node for Instance 1, as it is unlikely that both Virtual SQL Servers will fail over at the same time. However, with drag and drop, it is possible to move the primary for VSQL2 to node2 and the backup to node1. Now neither of the Virtual SQL Servers has a backup. Both node1 and node2 are primary for Instance1 and cannot also act as a backup for another instance having the same name. Select tasks from a menu Right-click on a SQL Server resource in either the Name column or a server cell to see the available options. HP PolyServe Software for Microsoft SQL Server administration guide 105

106 Virtual SQL Servers and Virtual SQL instances Most of the available options are described under Virtual SQL Server procedures on page 71. For information about rehosting, see Rehost a Virtual SQL Server on page 68. For information about adding a new virtual SQL instance, see Add a Virtual SQL instance on page 60. Virtual MSDTC and Virtual MSDTC Service Most of the available options are described under Other Virtual MSDTC procedures on page 85. For information about rehosting, see Rehost a Virtual MSDTC on page 83. Virtual SSAS and Virtual SSAS instances Most of the available options are described under Other Virtual SSAS procedures on page 97. For information about rehosting, see Rehost a Virtual SSAS on page 95. For information about adding a new virtual SSAS instance, see Add a Virtual SSAS instance on page Using the Applications tab

107 9 Instance Aliasing The Instance Aliasing feature can be used to map your existing legacy SQL connections to the Virtual SQL Server connections used with HP PolyServe Software. SQL clients can then continue to use the legacy connection string to access the SQL database in its new location. Overview The mappings from legacy SQL connections to the new Virtual SQL Server connections are created via the PolyServe Management Console and then stored in the Instance Aliasing mapping file, ia.conf. When clients connect via the legacy SQL connections, the mapping information is used to connect the clients to the Virtual SQL Server providing the appropriate virtual SQL instance. HP PolyServe Software provides a PolyServe SQL Browser Service that can perform the mapping operations for both default and named virtual SQL Server instances, and can also handle connections for SQL Server instances that have not been virtualized. This service must be enabled if you will be mapping named instances. When the PolyServe SQL Browser Service is enabled, it is used instead of the Microsoft SQL Browser Service, which cannot handle mappings for virtual named instances or name-to-name redirection. If you are mapping only default SQL Server instances, enabling the PolyServe SQL Browser Service is optional. Instance Aliasing port considerations Legacy SQL mappings require the legacy port to be unused by other SQL Server instances. If a port conflict does exist, Instance Aliasing will detect the conflict and remove the legacy SQL mapping from that port. On each node, the port assigned to a legacy mapping cannot also be used by any real instance, named or default, installed on that node. Move the mapping file The Instance Aliasing mapping file, ia.conf, is installed with HP PolyServe Software for Microsoft SQL Server. By default, the file is placed in the following location on the drive where you installed HP PolyServe Software: %PROGRAMFILES%\Polyserve\matrixserver\conf\ia.conf Before configuring Instance Aliasing, you will need to move this file to a PSFS filesystem that can be accessed by all nodes in the matrix. All nodes should use the same drive letter or mount point for the filesystem. Configure Instance Aliasing To configure Instance Aliasing, select Tools > SQL Instance Aliasing. HP PolyServe Software for Microsoft SQL Server administration guide 107

108 Configure Instance Aliasing settings The Instance Aliasing feature needs some configuration information to operate properly. Click Advanced on the Instance Aliasing window to open the Advanced Settings dialog. 108 Instance Aliasing

109 Mapping file location. Specify the location of the ia.conf file. The file should be located on a PSFS filesystem that can be accessed by all nodes in the matrix. All nodes should use the same drive letter or mount point for the filesystem. Refresh rate synch interval. Select the poll interval, in seconds, for checking the ia.conf file for configuration changes. The default is 10 seconds. Enable the Polyserve SQL Browser Service. If you are mapping named SQL Server instances, you will need to enable the PolyServe SQL Browser Service. This service is then used instead of the Microsoft SQL Browser Service, which cannot handle mappings for virtual named instances or name-to-name redirection. After completing your entries, click OK to return to the Instance Aliasing window. Your settings will not take effect until you click OK on the Instance Aliasing window. Map default instances If your legacy SQL connections are for default instances, use the Default instance remapping table on the Instance Aliasing window. To create a mapping to the Virtual SQL Server providing access to the new default virtual SQL instance, click New. The Add Default Alias window appears. From legacy IP. Enter the IP address to which clients connected when using the legacy default instance. Port. The port used by the legacy default instance must be To virtual IP. Enter the IP address used by the Virtual SQL Server providing the new default virtual SQL instance. NOTE: Aliasing does not verify the specified IP address. Be sure to enter an IP address that corresponds to a Virtual SQL Server. Port. Type the port number for TCP/IP Sockets that the SQL Server instance should listen on. (You specified this number on the Add Virtual SQL Instance window when you added the SQL Server instance to the Virtual SQL Server.) Click OK to return to the Instance Aliasing window. Your entry will be added to the ia.conf file when you click OK on the Instance Aliasing window. HP PolyServe Software for Microsoft SQL Server administration guide 109

110 Map named instances If your legacy SQL connections are for named SQL instances, use the Named instance remapping table on the Instance Aliasing window. To create a mapping to the Virtual SQL Server providing access to the new named virtual SQL instance, click New. The Add Named Alias window appears. From legacy IP. Enter the IP address to which clients connected when using the legacy named instance. Port. Enter the port number used by the legacy named instance. To Virtual IP. Enter the IP address used by the Virtual SQL Server that will be providing the new named Virtual SQL instance. NOTE: Instance Aliasing does not verify the specified IP address. Be sure to enter an IP address that corresponds to a Virtual SQL Server. Port. Enter the port number for TCP/IP Sockets that the SQL Server instance should listen on. (You specified this number on the Add Virtual SQL Instance window when you added the SQL Server instance to the Virtual SQL Server.) Sql Browser connection string. Specify the names of the legacy server and the legacy instance. Then select the SQL Server version that applies to the legacy instance. Click OK to return to the Instance Aliasing window. Your mapping entry will be added to the ia.conf file when you click OK on the Instance Aliasing window. Modify Instance Aliasing mappings To change the mapping for a default or named legacy SQL Server instance, select the appropriate entry on the Instance Aliasing window and then click Edit. You can then change the mapping as necessary on the Edit Default Alias or Edit Named Alias dialog. Your changes will be added to the ia.conf file when you click OK on the Instance Aliasing window. 110 Instance Aliasing

111 Delete Instance Aliasing mappings To remove the mapping for a default or named legacy SQL Server instance, select the appropriate entry on the Instance Aliasing window and then click Delete. Recommendations for monitoring Instance Aliasing We recommend that you create the following device monitor and notifiers to assist with monitoring Instance Aliasing operations. NTSERVICE device monitor. Create the monitor with the default parameters and add all nodes participating in Instance Aliasing to the monitor. (See Configure device monitors in the HP PolyServe Matrix Server administration guide for more information about creating the monitor.) This monitor will raise an Alert on the PolyServe Management Console if the NT Service goes down. A notifier triggered by the Alert that is generated by a probe failure of the NTSERVICE device monitor. (The Alert is event 4604.) See Configure Event Notifier Services in the HP PolyServe Matrix Server administration guide for more information about creating notifiers. Create a linked server When creating a linked server to a virtualized SQL Server instance, you must specify the actual Virtual SQL Instance for parameter. Using an aliased SQL name (such as an Instance Aliasing name) in is not supported. For example: @provider ='virtualsql1\instance1' HP PolyServe Software for Microsoft SQL Server administration guide 111

112 112 Instance Aliasing

113 10 Troubleshooting This chapter describes the following issues: Install/uninstall issues: SQL Server 2005 installation takes too long Installations via a Microsoft Terminal Services client Installer reports a failure Uninstall problems Connection issues: DNS misconfiguration causes Virtual SQL Server connection to fail Connection error with Windows authentication Windows authentication fails with SQL Server replication Client receives error when connecting via an alias Cannot authenticate on local machine with virtual hostname Error when creating a Virtual SQL Server An attempt to virtualize a SQL Server instance fails with the error A member could not be added to or removed from the local group because the member does not exist Cannot access a Virtual SQL instance from the active node SQL Server 2005 instance does not start Virtualized SSAS service does not start and reports an invalid request address Error when creating a distributor for replication Install/uninstall issues SQL Server 2005 installation takes too long Under certain circumstances, the SQL Server 2005 Setup program can take a long time to complete. This is a known Microsoft issue. Microsoft has developed a hotfix that corrects this problem. See the following Microsoft Knowledge Base article for more information about the problem and its resolution. You will need to contact Microsoft to obtain the hotfix described in the article. If you choose to implement the workaround specified in the Microsoft article, do not use Method 1, which disables TCP/IP. Matrix Server requires TCP/IP to function. Installations via a Microsoft Terminal Services client You must use an administrative console when installing SQL Server and Service Packs over a Microsoft Terminal Services Client connection. Otherwise, the Terminal Services Client will run in application mode, which causes the installation to fail. No information will be written to the SQL logs. To invoke an administrative console, do the following: HP PolyServe Software for Microsoft SQL Server administration guide 113

114 Start > Run > mstsc /console Installer reports a failure When installing certain SQL Server service packs or hotfixes, the Multi-Node Installer may report that the installation failed. Typically these installations actually succeeded. To verify this, you will need to look at the Microsoft installation logs for the service pack or hotfix that you were installing. The following information may help you determine the location of the logs. SQL Server 2005 core and components The following Microsoft document describes how to locate the log files: This Microsoft document describes how to read the files: SQL Server 2005 service packs and hotfixes For Service Pack 1, check the hotfix.log file in the %windir%\hotfix directory. For Service Pack 2, check the summary.txt file in the following directory: %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\HotFix Uninstall issues You may encounter various issues when uninstalling SQL Server 2005 instances. The following Microsoft Knowledge Base articles can help with failed uninstalls. If you receive an error when uninstalling multiple named instances of SQL Server 2005, see the following article: If you encounter an error when uninstalling SQL Server 2005 SP1, see the following article: If a SQL Server 2005 uninstall fails for any other reason, check the following article: Connection issues DNS misconfiguration causes connection failure The following error can appear when attempting to connect a Virtual SQL Server running locally on the cluster. SSPI handshake failed with error code 0x c while establishing a connection with integrated security; the connection has been closed. [CLIENT: XXX.XXX.XXX.XXX] 114 Troubleshooting

115 Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: XXX.XXX.XXX.XXX] The error occurs because the Virtual SQL Server is not properly registered with DNS or does not register a correct SPN in the domain. Domain Name Service (DNS) is the backbone of Active Directory (AD) and the primary name resolution mechanism for Windows. If DNS is not configured correctly, Windows authentication may fail. To verify that DNS is correctly configured for the Virtual SQL Server, ensure that the following tests are successful. 1. Ping the Virtual SQL Server. For example: C:\>ping vqar13s11 Pinging vqar13s11.ad1.polyserve.com [ ] with 32 bytes of data: Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Ping statistics for : Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms NOTE: If the ping fails, make sure an A record is created in DNS for the hostname. 2. Ping the virtual SQL Server IP address. For example: C:\>ping -a Pinging vqar13s11.ad1.polyserve.com [ ] with 32 bytes of data: Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Ping statistics for : Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms NOTE: If the ping does not return the fully qualified hostname, make sure a PTR record is created for the virtual IP. 3. Nslookup the Virtual SQL Server. For example: C:\>nslookup vqar13s11 Server: qadc1.ad1.polyserve.com Address: Name: vqar13s11.ad1.polyserve.com Address: NOTE: If the nslookup fails, make sure an A record is created in DNS for the hostname. HP PolyServe Software for Microsoft SQL Server administration guide 115

116 4. Nslookup the Virtual SQL Server IP address. For example: C:\>nslookup Server: qadc1.ad1.polyserve.com Address: Name: vqar13s11.ad1.polyserve.com Address: NOTE: If the nslookup fails, make sure a PTR record is created in DNS for the virtual IP. Nslookup may require you to set type=ptr and lookup the in-addr reverse form of the IP. For example: C:\>nslookup Default Server: qadc1.ad1.polyserve.com Address: > set type=ptr > in-addr.arpa Server: qadc1.ad1.polyserve.com Address: in-addr.arpa name = vqar13s11.ad1.polyserve.com > Server: qadc1.ad1.polyserve.com Address: in-addr.arpa name = vqar13s11.ad1.polyserve.com When a SQL client uses integrated security (SSPI) to connect to a SQL Server, the SQL driver authenticates the client via the strong network authentication, Kerberos first. If Kerberos is not available, NTLM authentication is then used to authenticate the client. Kerberos authentication is used only if the following prerequisites are met: Both the client and server computers are running Windows 2000 SP3 or higher. Both the client and server computers are part of the same domain or trusted domains. The SQL Server service SPN is registered with Active Directory. The SQL Server instance is listening on TCP/IP. The SQL client is connecting over TCP/IP. When a SQL client uses integrated security (SSPI) to connect to a SQL Server, the SQL driver authenticates the client via the strong network authentication, Kerberos first. If Kerberos is not available, NTLM authentication is then used to authenticate the client. Kerberos authentication is used only if the following prerequisites are met: Both the client and server computers are running Windows 2000 SP3 or higher. Both the client and server computers are part of the same domain or trusted domains. The SQL Server service SPN is registered with Active Directory. The SQL Server instance is listening on TCP/IP. The SQL client is connecting over TCP/IP. Kerberos uses a domain unique identifier, Service Principal Name (SPN), to identify a resource within a network. An SPN for SQL Server is composed of three components: ServiceClass: the class of service. MSSQLSvc is for SQL Server. 116 Troubleshooting

117 Host: the fully qualified domain name for the computer running the SQL Server service. Port: the TCP port that the SQL Server service is listening on. An example of a valid SPN for SQL Server is: MSSQLSvc/vqar13s11.ad1.polyserve.com:50004 When connecting to SQL Server via Kerberos, the client SQL driver uses the Winsock API (gethostbyname and gethostbyaddr) to resolve the SQL Server fully qualified name to form an SPN for the target SQL Server. Whether the SPN is valid depends entirely on DNS name/address resolution. If the client-formed SPN is invalid, the SSPI interface retries by looking up an SPN in Active Directory. If an SPN does not exist in AD for the SQL Server, Kerberos authentication is not used and the logon switches to an NTLM authentication. A valid SPN for SQL Server is assigned to two types of containers. When the SQL Server service account is a domain administrator or the local system account, an SPN for SQL Server is automatically registered and assigned to the hostname container when SQL Server starts up. If the SQL Server service account is not a domain administrator or the local system account, the SPN for the SQL Server container is the service account. The SETSPN utility can be used to register a SQL Server SPN for the service account. (The utility is available as part of Windows 2003 Support Tools on the Install media or Windows 2000 Resource Kit Tool referenced below.) For example: SETSPN.EXE -A MSSQLSvc/vqar13s11.ad1.polyserve.com:50004 SQLsvc NOTE: You must be a domain administrator to run the setspn command. Because Kerberos authentication will try to use the first SQL Server SPN that it finds in Active Directory, it is important to have only one SPN for each SQL Server service and to assign the correct container to each SPN. To gather a list of the current SPNs for SQL Server in Active Directory, use the attached queryspn VBScript. For example: C:\>cscript queryspn.vbs MSSQLSvc/* find "vqar13s11" -- MSSQLSvc/vqar13s11.ad1.polyserve.com:50004 To delete an existing SPN, run setspn with -D. For example: C:\>setspn -D MSSQLSvc/vqar13s11.ad1.polyserve.com:50004 vqar13s11 Unregistering ServicePrincipalNames for CN=Administrator,CN=Users,DC=pdxad1, DC=polyserve,DC=com MSSQLSvc/vqar13s11.pdxad1.polyserve.com:50004 Updated object References The following Microsoft documents provide additional information: Windows 2000 Resource Kit Tool: Setspn.exe DisplayLang=en How to: Enable Kerberos Authentication on a SQL Server Failover Cluster How to use Kerberos Authentication in SQL Server HP PolyServe Software for Microsoft SQL Server administration guide 117

118 Microsoft NTLM queryspn.vbs script ' Copyright (c) Microsoft Corporation ' File: queryspn.vbs ' Contents: Query a given SPN in a given forest to find the owners ' History: 7/7/2004 Craig Wiand Created Option Explicit Const DUMP_SPNs = True Dim oconnection, ocmd, orecordset Dim ogc, onsp Dim strgcpath, strclass, strspn, stradoquery Dim vobjclass, vspns, vname ParseCommandLine() '--- Set up the connection --- Set oconnection = CreateObject("ADODB.Connection") Set ocmd = CReateObject("ADODB.Command") oconnection.provider = "ADsDSOObject" oconnection.open "ADs Provider" Set ocmd.activeconnection = oconnection ocmd.properties("page Size") = 1000 '--- Build the query string --- stradoquery = "<" + strgcpath + ">;(serviceprincipalname=" + strspn + ");" & _ "dnshostname,distinguishedname,serviceprincipalname,objectclass," & _ "samaccountname;subtree" ocmd.commandtext = stradoquery '--- Execute the query for the object in the directory --- Set orecordset = ocmd.execute If orecordset.eof and orecordset.bof Then Wscript.Echo "No SPNs found!" Else While Not orecordset.eof Wscript.Echo orecordset.fields("distinguishedname") vobjclass = orecordset.fields("objectclass") strclass = vobjclass( UBound(vObjClass) ) Wscript.Echo "Class: " & strclass If UCase(strClass) = "COMPUTER" Then Wscript.Echo "Computer DNS: " & orecordset.fields("dnshostname") Else Wscript.Echo "User Logon: " & orecordset.fields("samaccountname") End If If DUMP_SPNs Then '--- Display the SPNs on the object --- vspns = orecordset.fields("serviceprincipalname") For Each vname in vspns Wscript.Echo "-- " + vname Next End If Wscript.Echo orecordset.movenext Wend 118 Troubleshooting

119 End If orecordset.close oconnection.close Sub ShowUsage() Wscript.Echo " USAGE: " & WScript.ScriptName & _ " SpnToFind [GC Servername or Forestname]" Wscript.Echo Wscript.Echo " EXAMPLES: " Wscript.Echo " " & WScript.ScriptName & _ " MSSQLSvc/MySQL.company.com:1433" Wscript.Echo " " & WScript.ScriptName & _ " HOST/Server1 Corp.com" Wscript.Quit 0 End Sub Sub ParseCommandLine() If WScript.Arguments.Count <> 1 And WScript.Arguments.Count <> 2 Then ShowUsage() Else strspn = WScript.Arguments(0) If WScript.Arguments.Count = 2 Then strgcpath = "GC://" & WScript.Arguments(1) Else '--- Get GC -- Set onsp = GetObject("GC:") For Each ogc in onsp strgcpath = ogc.adspath Next End If End If End Sub Connection error with Windows authentication When connecting to a SQL Server instance using local Windows authentication, you may receive the following error: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. This error is addressed in the following Microsoft Knowledge Base article: Windows authentication fails with SQL Server replication When replication is set up using SQL Server tools, by default the replication agents are configured to use Windows authentication. However, if at any time the replication agent runs on the same machine as the replication distributor or publisher, the agent will fail to connect to those instances. This situation occurs because of a SQL Server problem described in the following Microsoft Knowledge Base article: To work around this problem, you will need to modify the steps in the replication job to use SQL authentication instead of Windows authentication. Add the following options: For the log reader agent: HP PolyServe Software for Microsoft SQL Server administration guide 119

120 logread [-?] -Publisher server_name[\instance_name] -PublisherDB publisher_database [-DistributorLogin distributor_login] [-DistributorPassword distributor_password] [-DistributorSecurityMode [0 1]] // set to 1 for SQL authentication [-PublisherSecurityMode [0 1]] // set to 1 for SQL authentication [-PublisherLogin publisher_login] [-PublisherPassword publisher_password] For the distributor job: [-DistributorLogin distributor_login] [-DistributorPassword distributor_password] [-DistributorSecurityMode [0 1]] // set to 1 for SQL authentication [-SubscriberLogin subscriber_login] [-SubscriberPassword subscriber_password] [-SubscriberSecurityMode [0 1]] // set to 1 for SQL authentication For the merge agent job: [-DistributorLogin distributor_login] [-DistributorPassword distributor_password] [-DistributorSecurityMode [0 1]] // set to 1 for SQL authentication [-PublisherLogin publisher_login] [-PublisherNetwork publisher_network] [-PublisherPassword publisher_password] [-PublisherSecurityMode [0 1]] // set to 1 for SQL authentication [-SubscriberLogin subscriber_login] [-SubscriberPassword subscriber_password [-SubscriberSecurityMode [0 1]] // set to 1 for SQL authentication For the queue reader agent: [-DistributorLogin distributor_login] [-DistributorPassword distributor_password] [-DistributorSecurityMode [0 1]] // set to 1 for SQL authentication For the snapshot agent: [-DistributorLogin distributor_login] [-DistributorPassword distributor_password] [-DistributorSecurityMode [0 1] ] // set to 1 for SQL authentication For more information about Replication Agent Utilities, see the Microsoft article Replication Agent Utilities, available at the following website: Cannot authenticate on the local machine with a virtual host name To successfully authenticate on the local machine by the virtual host name (for example, a Virtual SQL Server, Virtual Host, or Virtual CIFS Server) the DisableLoopbackCheck flag must be set. Microsoft KB article documents the following procedure to do this. To set the DisableLoopbackCheck registry entry to 1, follow these steps on each cluster node: 1. Click Start, click Run, type regedit, and then click OK. 120 Troubleshooting

121 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa 3. Right-click Lsa, point to New, and then click DWORD Value. 4. Type DisableLoopbackCheck, and then press ENTER. 5. Right-click DisableLoopbackCheck, and then click Modify. 6. In the Value data box, type 1and then click OK. 7. Exit Registry Editor. 8. Restart the computer for the change to take effect. NOTE: When Matrix Server is installed, it can create the appropriate registry key automatically if desired. Error when creating a Virtual SQL Server Because the installation of MSCS (Microsoft Cluster Services) modifies key system files, you must completely remove MSCS before creating a Virtual SQL Server. If you do not uninstall MSCS, you will see the following error when adding a Virtual SQL Server: See the following Microsoft Knowledge Base article for more information about removing MSCS. Failure to virtualize a SQL instance If a SQL instance has the service account set to a local user or administrator, an attempt to virtualize the instance will fail with this message from the operating system: A member could not be added to or removed from the local group because the member does not exist To correct this problem, you will need to set the service account for the instance to either a domain user or LocalSystem on all nodes. When using SQL Server Configuration Manager to change the user for the service account, be sure to type the new user name using NTLM-style credentials (DOMAIN\user). You can also browse for the appropriate user account. Cannot access a Virtual SQL instance from the active node To successfully access a Virtual SQL instance on the active node, the following requirements must be met: HP PolyServe Software for Microsoft SQL Server administration guide 121

122 An alias must exist to direct the Virtual SQL instance. HP PolyServe Software creates this alias. To verify that the alias exists for a SQL Server instance, use Configuration Manager > Alias. The instance must be listening on TCP. Check the SQL log to verify this. Forward and reverse lookup works for the instance. See DNS requirement for Virtual SQL Servers on page 57, for more information. The instance is registered correctly in Active Directory. Check for a valid SPN. SQL Server 2005 instance does not start If the computer name for a node has ever been changed, the SQL 2005 instances installed on that node may not start in the following circumstances: During virtualization During failover After upgrading to a later version of HP PolyServe Software for Microsoft SQL Server To work around this issue, change the service account group names to match the current name of the node. Next, remove the node from the domain and then rejoin it. The SQL Server 2005 instances will now start properly. Virtualized SSAS instance does not start and reports an invalid request address After a SSAS instance is virtualized, the SSAS service does not start and the following error is reported: The service cannot be started: The following system error occurred: The request address is not valid in its context. This error occurs when an attempt is made to start a virtualized named SSAS instance on a primary node when the default SSAS instance is also installed on that node and has been started natively. By default, the default instance is configured to listen on :2383. An attempt to start another instance with another IP address, but listening on port 2383, will fail with the above message. To correct this situation, take one of the following actions: Virtualize the default instance before virtualizing any named instances. Do not install a default instance on a node where named instances are installed. Error when creating a distributor for replication Typically you connect to HP PolyServe Software for Microsoft SQL Server via <virtual name>,<tcp port>. However, this connection method does not work when configuring a distributor for replication and results in the following error. 122 Troubleshooting

123 This situation is by design. Internally, Microsoft uses (i.e., vsql\instance) for verification, while Enterprise Manager uses the registered server name (i.e., vsql,port#). Because the values do not match, the attempt to create the distributor fails. To work around this limitation, it is necessary to connect to HP PolyServe Software for Microsoft SQL Server via <servername>\<instancename>. This type of connection is not guaranteed from the remote Enterprise Manager because of name resolution and the custom TCP port used for HP PolyServe Software for Microsoft SQL Server. Instead, we recommend that you launch Enterprise Manager either locally on the active node or within the local subnet. You can then create the distributor. When you create the distributor, a Replicator Monitor should also be created for you. Configuring publication database(s) and selecting qualified subscriber(s) is similar to configuring a stand-alone server, as shown below. HP PolyServe Software for Microsoft SQL Server administration guide 123

124 Next, create a publication and specify the desired replication model. 124 Troubleshooting

125 NOTE: Queued updating is supported only if the changes are queued in a SQL Server database. Queued updating via MSMQ is not supported for HP PolyServe Software for Microsoft SQL Server. Next, specify the database object(s) as part of the publication. Now accept and commit the settings for the publication. HP PolyServe Software for Microsoft SQL Server administration guide 125

126 After the publication is initialized, specify the target subscriber and database for a push subscription. Specify the desired frequency for each data distribution. Initialize the subscriber s data. 126 Troubleshooting

127 Specify the subscription mode. Finally, commit and start the subscription. HP PolyServe Software for Microsoft SQL Server administration guide 127

128 128 Troubleshooting

129 11 Upgrade production SQL Servers This chapter describes how to upgrade production SQL servers and components of the underlying environment that can affect SQL server availability. The procedures include upgrades to SQL instances and general machine upgrades such as Microsoft Windows service packs, firmware, and third-party software. The upgrade procedures minimize interruptions to SQL server availability by leveraging the clustering capabilities of Matrix Server. Also, if an error occurs, the DBA can restore the original machine state. General upgrade process The major steps involved in an upgrade are as follows. 1. Plan the upgrade It is important to plan upgrades to highly available production SQL servers. You should define the following: Who will perform the upgrade? This person must be experienced with your environment and with Matrix Server. Which applications and users will be affected? An application will be affected if it has a database residing on a virtual SQL server. Plan to notify affected users before and after the upgrade. When to upgrade? Query users for the best time to perform the upgrade, and consider a time window in which availability requirements are less strict. What if something goes wrong? You will need to determine what is a valid machine state, and how to back it up and restore it in the minimum amount of time. Also ensure that all support agreements are in place and that contact information is updated. Will other components in the machine be affected? For example, a SQL service pack upgrade to one instance affects all other instances on the same machine. 2. Test the upgrade It is important to run the upgrade in a test environment to ensure that the upgrade will function successfully on the production server. Testing also ensures that there will be no surprises during or after the upgrade. For example, to test a SQL server upgrade, you should create a typical workload mix of your application s user transactions and then measure different machine parameters such as CPU or I/O load. When the test environment is ready, complete these steps: 1. Test the current configuration and create a baseline of the results. 2. Record the start time and then perform the upgrade on the test machine. 3. After the upgrade, check the event log and setup files for errors. 4. Record the end time to get an estimate of total down time. HP PolyServe Software for Microsoft SQL Server administration guide 129

130 5. Run the workload tests again and compare the results with the baseline. We recommend that the test machine be identical to the production machine. For example, the two machines should contain the same components (including third-party applications such as anti-virus software) and the same settings (such as the /3G flag in boot.ini). Also ensure that the component versions match. The following generic components should be identical on the test and production machines. Number of SQL instances Settings of SQL instances SQL Service Packs SQL hot fixes Operating system version Operating system service packs Operating system security updates Matrix Server version SQL Server solution pack version Net CLR service packs Network card and firmware Network card settings Number of network cards HBA card and firmware Number of NBA cards Number of CPUs Amount of physical memory Third-party software.net CLR version If you are unable to create an identical test machine, we recommend that you create a scaled-down version of your production machine and test any upgrades on it. Be sure to scale down the workload as well. Although a scaled-down machine deviates from the real environment, it will enable you to verify that the dependency among components does not affect SQL server availability after the upgrade. 3. Back up the current machine state Before performing the upgrade, you should back up the current state of the production machine. The backup should include the general machine-wide state and the SQL instance-specific state. The machine-wide state includes the following: Registry settings Machine name, network settings, accounts Shared SQL files and DLL Operating system The SQL instance-specific state includes the following: Data (master database, model database, user database) Logins DTS packages Before starting the upgrade, verify that you can restore the backup onto your test machine. 130 Upgrade production SQL Servers

131 4. Notify users of upgrade start For a planned upgrade, users should anticipate application down time and prepare for it. However, notifying users that the upgrade is starting shows that the process is under control and that the plan is being executed properly. 5. Apply the upgrade Upgrade the production server as described later in this chapter. Upgrade procedures are provided for SQL instance upgrades and general machine upgrades such as operating system service packs. 6. Confirm the upgrade If the upgrade was successful, check the SQL error logs and event logs for any errors. Also check basic database access by connecting with the Query Analyzer and querying one of the databases.if the upgrade failed, return the machine to the exact machine state before the upgrade. To do this, perform a restore using your backup files. 7. Notify users of upgrade completion When the upgrade is complete, notify users that they can resume their regular database activities. 8. Back up the machine state Back up the new machine state and create a base line. Upgrade SQL instances Be sure to apply the procedure to your test system before upgrading a production machine. Upgrade considerations When performing an upgrade, you should be aware of the following: Because the upgrade is done per instance, it should be repeated for each instance. Microsoft supports a machine running SQL instances with different versions. Rolling upgrades are not supported. You cannot access the database while the upgrade is running. Upgrades need to be performed during change management windows. Therefore, you should restrict access to the database to avoid corruption caused by the upgrade. If multiple SQL Service Monitors (vsql Instances) share backup nodes, the instances will be disabled during maintenance mode. These instances will need to be enabled during the upgrade process as noted below. On a machine with multiple SQL Server 2005 instances, running the first upgrade may upgrade the version of the shared file DLLs. See Instance-Aware components on page 50, for more information. If you need to reboot the machine, all of the instances will be affected. HP PolyServe Software for Microsoft SQL Server administration guide 131

132 Upgrade procedure To perform the upgrade, complete these steps: 1. Move the Virtual SQL Server (VSQL) associated with the instance to maintenance mode. Select the Virtual SQL Server on the PolyServe Management Console, right-click, and select Maintain. 2. If the instance being upgraded is disabled on any backup nodes, select the instance on the PolyServe Management Console, right-click, and select Enable before proceeding. 3. Upgrade the SQL instance on the backup node. 4. Repeat steps 2 and 3 for each backup Virtual SQL Instance. 5. Upgrade the instance on the primary node. 6. Return the Virtual SQL Server to operational mode. Select the Virtual SQL Server associated with the instance on the PolyServe Management Console, right-click, and select Operate. Multiple instance upgrades You may want to perform a multiple-instance upgrade on consolidated servers that hold many instances. These servers typically use one of the configurations described earlier and the same general procedures can be used. However, you should be aware of the following: A manual upgrade will probably necessitate a reboot, which will affect all of the instances on the server. To avoid this, we recommend that you use an unattended install, which does not require a reboot. Because the instances have a shared location, during the upgrade there can be more than one version of SQL Server on the machine. General machine upgrades This procedure applies to the following types of upgrades: Operating system, include service packs and hotfixes Firmware Third-party software These upgrades may require a reboot; however, you can minimize machine downtime by perform a rolling upgrade. In this scenario, you will need to fail over the Virtual SQL Server from the primary node, and then upgrade that node while the Virtual SQL Server resides on the backup node. Clients will see a small downtime from two failovers (a failover to the backup node before the upgrade, and a failback after the upgrade) instead of a full upgrade downtime as in a non-clustered environment. The procedure first upgrades the backup node and then upgrades the primary. Upgrade the Backup Node Complete these steps: 1. Ensure that all virtual SQL servers are active on their primary nodes. 2. Disable hosting on the backup node. 3. Apply the upgrade (for example, a service pack). 4. Enable hosting on the backup node. 132 Upgrade production SQL Servers

133 Upgrade the Primary Node Complete these steps: 1. Disable hosting on the primary node and verify that all virtual hosts have moved to a backup node. 2. Apply the upgrade. 3. Enable hosting on the primary node. By default, Virtual SQL Servers are set to NOFAILBACK and will remain on the backup node. If you want a Virtual SQL Server to fail back to the primary node, you will need to disable an instance associated with the Virtual SQL Server on the backup node currently hosting the Virtual SQL Server. The Virtual SQL Server will then fall back to the primary node. HP PolyServe Software for Microsoft SQL Server administration guide 133

134 134 Upgrade production SQL Servers

135 A Configure SQL Server Reporting Services HP PolyServe Software can be used to provide High Availability for SQL Server Reporting Services that are deployed in a scale-out configuration. In this configuration, the matrix nodes host the reporting service generation and scheduling. The report definitions are in the reporting service database, which is a SQL instance located on a PSFS filesystem that can be accessed by all of the nodes. Clients use a Matrix Server virtual host to access the matrix nodes. NOTE: Although the screen captures shown in this appendix are from an earlier version of the HP PolyServe Software product, the procedure is the same in HP PolyServe Software for Microsoft SQL Server Configure Reporting Services To configure reporting services with HP PolyServe Software, complete these steps on each node: 1. Install SQL Server (optional) and the Report Server on each node. HP PolyServe Software for Microsoft SQL Server administration guide 135

136 2. Create a Virtual SQL Server to serve as the configuration database. This Virtual SQL Server does not need to be on the same node(s) as the Report Server, making the SQL Server installation in step 1 optional. To create the Virtual SQL Server, select Matrix > Add > Add Virtual SQL Server. (For information about filling out the Add Virtual SQL Server window, see Configure Virtual SQL Servers on page 57.) Be sure to configure the Virtual SQL Server on all nodes that will be providing reporting services. 3. Create a Virtual SQL Instance for the configuration database. Select the Virtual SQL Server created in step 1, right-click, and select Add Virtual SQL Instance. In the Name field, select the SQL Server instance with the reporting database. Configure Report Server for SQL Server 2008 For SQL Server 2008, take these steps: 136 Configure SQL Server Reporting Services

137 1. Configure the Service Account. 2. Configure the Web Service URL. 3. Using the Reporting Services Configuration Manager, configure the Report Server Database and specify the appropriate credentials. 4. Configure Report Server on each node as described below. 5. Configure the Report Manager URL. 6. Configure Settings. 7. Configure the Execution Account. 8. Configure Encryption Keys. HP PolyServe Software for Microsoft SQL Server administration guide 137

138 9. On the Scale-out Deployment page, add servers to the deployment. See the Microsoft Reporting Services documentation for more information about configuring Report Server. Configure Report Server for SQL Server 2005 For SQL Server 2005, take these steps: 1. Start Report Server. 2. Configure Report Server Virtual Directory. 3. Configure Report Manager Virtual Directory. 4. Configure Windows Service Identity. 5. Configure Web Service Identity. 6. Configure Database Connection, specifying the Virtual SQL Instance that you created in step Configure SQL Server Reporting Services

139 7. Configure Backup/Restore Encryption Keys. 8. Initialize Report Services. 9. Configure /Execution Account as desired. See the Microsoft Reporting Services documentation for more information about configuring Report Server. Configure high availability support All of the reporting services should now point to the same configuration database. To provide High Availability for the reporting services, take the following steps: HP PolyServe Software for Microsoft SQL Server administration guide 139

140 1. Create a Matrix Server virtual host that clients can use to access the reporting services database. On the PolyServe Management Console, select Matrix > Add > Add Virtual Host. Configure the virtual host on all nodes that will act as reporting servers. 2. Create an NTSERVICE device monitor for the IIS service on each node. (Select one of the servers, right-click, and select Add Device Monitor.) The name of the IIS NT service is W3SVC. Specify Yes to start the dependent services and set the number of retries to one. 3. Click Advanced and go to the Virtual Hosts tab. Select the virtual host that you created in step Configure SQL Server Reporting Services

141 4. Go to the Server tab and select all of the nodes that are acting as reporting servers. Then click OK. 5. Create a second NTSERVICE monitor for the reporting services NT service on each node. The name of the NT service is REPORTSERVER${instancename}, where {instancename} is the actual instance where Report Server is installed. (In this example, REPORTSERVER$INSTANCE1.) Then enter Yes to start the dependent services and set the number of retries to one. HP PolyServe Software for Microsoft SQL Server administration guide 141

142 6. Click Advanced. Go to the Virtual Hosts tab and select the virtual host configured in step 1. Next, go to the Servers tab and select all servers that will be acting as reporting servers. Then click OK. The configuration looks like this on the PolyServe Management Console. 7. Create a report and publish it as desired. Clients use the IP address of the virtual host to access the reporting database instead of using the server s IP address. For example: Configure SQL Server Reporting Services

143 If the primary node for the virtual host goes down, the virtual host will failover to a backup node and access will continue. Similarly, if either of the NTSERVICE device monitors detect a failure, the associated virtual host can fail over to a backup node. HP PolyServe Software for Microsoft SQL Server administration guide 143

144 144 Configure SQL Server Reporting Services

145 B Hosting Configurations for MS DTC The information in this appendix applies to MS DTC when it is managed by a Virtual SQL Server (the Manage msdtc option is enabled in the Virtual SQL Server configuration). If you are configuring MS DTC for high availability, as described in Chapter 4, refer to that chapter for MS DTC configuration information. Overview The information in this appendix applies to MS DTC when it is managed by a Virtual SQL Server (the Manage msdtc option is enabled in the Virtual SQL Server configuration). If you are configuring MS DTC for high availability, as described in Chapter 5, refer to that chapter for MS DTC configuration information. Overview The Microsoft Distributed Transaction Coordinator (MS DTC) is the transaction manager responsible for coordinating transaction atomicity across multiple resource managers. It ensures that an update of data (work) is either committed or rolled back on all servers that are participating in the transaction. As shown below, the client connects to Server A and invokes a remote call to Server B, which employs MS DTC to manage the transaction across these two servers. With the help of DTC, the work is guaranteed to either commit or rollback on both servers. HP PolyServe Software for Microsoft SQL Server utilizes the PSFS cluster filesystem, in which all nodes in the cluster can simultaneously read/write to a file on the shared disk. On failover, the backup node simply starts up SQL Server and mounts the data on the shared disk. There is relatively little cost in transition or data movement. Whether SQL Server is running as stand-alone or clustered, MS DTC is needed if SQL Server (or Virtual SQL Server) needs to maintain a transaction spanning across multiple data sources. Although, as shown in the following section, HP PolyServe Software can transparently virtualize DTC service on the active node (this option is enabled by checking the MSDTC checkbox), only one DTC-enabled HP PolyServe Software for Microsoft SQL Server administration guide 145

146 Virtual SQL Server can be active on a node. Other DTC-enabled Virtual SQL Servers will not be able to fail over to this node. Set up local MS DTC-enabled Virtual SQL Servers This configuration allows the host for the Virtual SQL Server to utilize the local DTC service for distributed transactions. The DTC service is attached to the Virtual SQL Server engine and will fail accordingly. To enable DTC on the local node, it must be configured to accept incoming transactions and perform outgoing transactions on the network. The following instructions are a recommended method of configuration, although your application needs may differ. 1. Open Component Services via Start > Programs > Administrative Tools. 2. Expand the Component Services folder and browse to the My Computer folder. 146 Hosting Configurations for MS DTC

147 3. Right-click the My Computer folder to open its Properties dialog. 4. Select the MSDTC tab. 5. Ensure that Use local coordinator is checked and then click Security Configuration. For more information, see Actions when configuring the Virtual MSDTC Service on page 81. HP PolyServe Software for Microsoft SQL Server administration guide 147

148 6. On the Security Configuration tab, the following Security Settings should be checked: Network DTC Access Allow Remote Clients Allow Remote Administration Allow Inbound Allow Outbound No Authentication Required. Enable XA Transactions 7. Click OK to commit the changes. DTC management can be enabled either when creating a Virtual SQL Server or by changing the properties for the Virtual SQL Server. Check Manage msdtc to enable DTC management. 148 Hosting Configurations for MS DTC

149 Set up a remote node for hosting DTC DTC can be configured to use a remote host, which can be either a dedicated node in the Matrix Server cluster or a stand-alone server outside of the cluster. This configuration offloads the DTC hosting and allows the Virtual SQL Servers to fail over while maintaining their DTC availability. The following procedure can be used to set up a remote node to host DTC. The procedure is a recommended method of configuration; however, your application needs may differ. HP PolyServe Software for Microsoft SQL Server administration guide 149

150 1. Open Component Services: Start > Programs > Administrative Tools 2. Expand the Component Services folder and browse to the My Computer folder 3. Right click the My Computer folder to open the Properties dialog. 4. Select the MSDTC tab. 5. Ensure that Use local coordinator is checked and then click Security Configuration. For more information, see Actions when configuring the Virtual MSDTC Service on page Hosting Configurations for MS DTC

151 6. On the Security tab, the following Security Settings should be checked: Network DTC Access Allow Remote Clients Allow Remote Administration Allow Inbound Allow Outbound No Authentication Required. Enable XA Transactions 7. Click OK to commit the changes. Set up local nodes to use Remote DTC When another node is used to host DTC, every local node participating in a Virtual SQL Server must be configured manually. Complete the following steps on each local node: 1. Open Component Services: Start > Programs > Administrative Tools. 2. Expand the Component Services folder and browse to the My Computer folder. HP PolyServe Software for Microsoft SQL Server administration guide 151

152 3. Right click the My Computer folder to bring up its properties dialog. 4. Select the MSDTC tab. 5. Ensure that Use local coordinator is unchecked and, at the Remote coordinator host name prompt, specify the remote node that is hosting DTC. Then stop the MSDTC service from Run > services.msc > Distributed Transaction Coordinator. 6. Open SQL Service Manager (Start > Programs > Microsoft SQL Server) and then restart the SQL Server service. This step is necessary to allow the new DTC change to take effect. 7. Set the startup method for the Distributed Transaction Coordinator service to Manual. 152 Hosting Configurations for MS DTC

153 Summary References DTC is quite important in a distributed environment. It is the middle man ensuring that all parties that participated in a transaction agree with the resulting outcome. The transaction is guaranteed to be either 100% committed or rolled back. Hosting DTC remotely on a dedicated node is easy to set up and use. HP PolyServe Software for Microsoft SQL Server works quite well in this scenario and has fewer restrictions regarding whether the hosting node is part of the same cluster that is using it. The following sources are for MSDTC on Windows In general, the information also applies to MSDTC on Windows 2008, with the exception of the minor GUI change described in the following article: How To Set Up a Local MS DTC to Point to a Remote MS DTC: How to enable network DTC access in Windows Server 2003: How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 cluster: Distributed Transactions: Microsoft tool to test DTC configuration: Microsoft tool to test the connection between the local SQL Server and the remote DTC host: displaylang=en Managing Accounts and Privileges: Failover Clustering Dependencies: Prerequisite Considerations for Adding a DTC Resource to a Cluster: HOWTO: Enable DTC Between Web Servers and SQL Servers Running Windows Server 2003: INFO: Configuring Microsoft Distributed Transaction Coordinator (DTC) to Work Through a Firewall: How To Troubleshoot MS DTC Firewall Issues: HP PolyServe Software for Microsoft SQL Server administration guide 153

154 MS KBs on DTC: Hosting Configurations for MS DTC

155 C Support and other resources HP technical support For worldwide technical support information, see the HP support website: Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: After registering, you will receive notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: HP PolyServe Software for Microsoft SQL Server administration guide 155

156 156 Support and other resources

157 Index A active-active configuration, 10 Active-Passive architecture, 9 Analysis Services service, restart, 92 Applications tab drag and drop, 105 manage configuration, 105 monitor error, 104 overview, 101 SQL resources, 101 Virtual MSDTC, 102 Virtual SQL Server, 101 Virtual SSAS, 103 authentication, Windows, 34 AUTOFAILBACK policy Virtual MSDTC, 78 Virtual SSAS, 90 B BUILTIN\Administrators group requirement, 34 C configuration Instance Aliasing, 107 SQL clients, 66 Virtual MSDTC, 77 Virtual SQL Instance, 60 Virtual SQL Server, 57 Virtual SSAS, 89 D database backups, 74 DNS requirement for Virtual MSDTC, 77 requirement for Virtual SQL Servers, 57 requirement for Virtual SSAS, 89 troubleshoot failures, 114 drag and drop, on Applications tab, 105 F failover, 11 failover policy, 63 H HP PolyServe Software for Microsoft SQL Server overview, 9 HP technical support, 155 I ia.conf file, Instance Aliasing, 107 in-place upgrade, 37 prerequisites, 37 restrictions, 38 supported upgrades, 37 upgrade procedure, 38 installation Service Packs and hotfixes, 49 troubleshoot failures, 114 via Terminal Services client, 113 installation, SQL instance install SQL Server 2005 instance, 27 install SQL Server 2008 instance, 19 Maximum Memory setting, 33 operating system support, 13 overview, 13 prerequisites, 13 Instance Aliasing configure, 107 delete mappings, 111 ia.conf mapping file, 107 linked server, 111 map default instances, 109 map named instances, 110 modify mappings, 110 monitor operations, 111 overview, 107 PolyServe SQL Browser Service, 107 port considerations, 107 L legacy SQL instances, map to virtual instances, 107 linked server, create, 111 HP PolyServe Software for Microsoft SQL Server administration guide 157

158 M maintenance mode upgrades, 49 Virtual SQL Server, 70 Virtual SSAS, 97 many-to-one configuration, 10 Maximum Memory setting, 33 Mixed Mode authenication password requirement for SQL Server 2008, 14 MS DTC configure for high availability, 77 hosting configurations, 145 manage via Virtual SQL Server, 58 requirements for virtualizing, 77 MSDTC service monitor custom scripts, 64 custom starting/stopping actions, 65 event severity, 66 failover policy, 63 Post Start script, 65 Pre Stop script, 65 probe type, 64 recovery script, 65 script order, 66 service priority, 64 timeout and failure severity, 63 Multi-Node Install Wizard, 19 Multi-Node Upgrade Wizard, 49 N network configuration changes, 70 NOFAILBACK policy Virtual MSDTC, 78 Virtual SSAS, 90 P perfmon utility use with Virtual SSAS, 95 PolyServe SQL Browser Service, 107 progress report Virtual MSDTC, 79 Virtual SQL Server, 60 Virtual SSAS, 91 R registry keys, 12 Registry Replicator alert notifier, 70 rehosting Virtual SQL Server, 68 Virtual SSAS, 95 replication distributor configuration error, 122 Windows authentication failure, 119 replication on SQL instances, 61 Reporting Services, configure, 135 S server, remove from Virtual SQL Server configuration, 72 SQL Agent Mail, configure, 74 SQL Aqent, 74 SQL clients configure, 66 SQL configuration active-active, 10 many-to-one, 10 planning for, 10 SQL instance map legacy instances, 107 overview, 13 requirements for virtualization, 61 uninstall, 75 upgrade, 49 virtualization failure, 121 SQL Mail, configure, 74 SQL Server 2005 installation considerations, 17 installation prerequisites, 13 installation procedure, 27 supported OS, 13 upgrade considerations, 50 Instance-Aware components, 17 SQL Server 2008 additional information, 16 Filestream support, 15 installation considerations, 14 installation prerequisites, 13, 14 installation procedure, 19 Instance ID, 15 Instance-Aware components, 15 Mixed Mode authentication, 14 supported OS, 13 upgrade considerations, 50 SQL Server hotfixes, install, 49 SQL Server Profiler use with Virtual SSAS, 94 SQL Server Service Packs, install, 49 SQL servers upgrade production servers, 129 SQL service restart,

159 SQL service monitor, 62 custom scripts, 64 custom starting/stopping actions, 65 errors, clear, 73 event severity, 66 failover, 11 failover policy, 63 monitor error, 104 Post Start script, 65 Pre Stop script, 65 probe configuration, 62 probe type, 64 recovery script, 65 script order, 66 service priority, 64 timeout and failure severity, 63 SSAS 2005 instances, install, 19 SSAS 2008 instances, install, 17 SSAS instance requirements for virtualization, 92 SSAS service monitor clear errors, 99 custom scripts, 64 custom starting/stopping actions, 65 event severity, 66 failover policy, 63 optional components, 92 Post Start script, 65 Pre Stop script, 65 probe configuration, 93 probe type, 64 recovery script, 65 script order, 66 service priority, 64 timeout and failure severity, 63 Surface Area Configuration tool use with Virtual SSAS, 94 T TCP/IP port assignments, 34 technical support HP, 155 service locator website, 155 troubleshooting authenticate with virtual host name, 120 authentication failure with replication, 119 distributor configuration error, 122 DNS issues, 114 installation failures, 114 installation via Terminal Services client, 113 remove MSCS, 121 SQL instance does not start, 122 SQL Server 2005 installation, 113 SSAS instance does not start, 122 uninstall failures, 114 uninstall SQL instance, 75 Virtual SQL Instance access, 121 virtualization failure, 121 Windows authentication error, 119 U uninstall failures troubleshoot, 114 upgrade production SQL Servers, 129 upgrade, in-place, 37 upgrade, SQL instance considerations for SQL Server 2005, 50 considerations for SQL Server 2008, 50 location for product files, 49 log files, 51 maintenance mode, 49 overview, 49 upgrade procedure, 51 V Virtual MSDTC add node, 85 add Virtual MSDTC Service, 80 backup interface, 78 configure nodes for access, 82 create, 77 delete, 85 DNS requirement, 77 drag and drop, 105 enable or disable, 85 failback policy, 78 modify configuration, 85 on Applications tab, 102 primary interface, 78 prorgress reports, 79 rehost, 83 view status, 86 HP PolyServe Software for Microsoft SQL Server administration guide 159

160 Virtual MSDTC Service add to Virtual MSDTC, 80 configuration changes, 81 delete, 86 enable or disable, 86 errors, clear, 87 modify configuration, 86 on Applications tab, 102 optional components, 80 probe configuration, 80 remove server, 86 view alerts, 87 view status, 87 virtual data root, 80 Virtual MSDTC Service monitor add to Virtual MSDTC, 80 monitor error, 104 Virtual SQL Instance access issues, 121 add to Virtual SQL Server, 60 delete, 73 enable or disable, 73 instance does not start, 122 modify configuration, 72 monitoring, 69 on Applications tab, 101 optional components, 62 probe configuration, 62 replication, 61 revirtualize, 73 view status, 74 virtual data root, 61 Virtual SQL Server,modify configuration, 71 add node, 71 backup interface, 59 change MS DTC virtualization status, 71 configure, 57 create, 57 delete, 72 DNS requirement, 57 drag and drop, 105 enable or disable, 72 failback policy, 59 failover, 11 maintenance mode, 70 network configuration changes, 70 on Applications tab, 101 primary interface, 59 rehost, 68 remove from server, 72 TCP/IP assignments, 34 view on Management Console, 62 view status, 72 Virtual SQL Server: Active-Passive architecture, 9 Virtual SSAS add node, 97 backup interface, 90 configure, 89 create, 89 delete, 98 DNS requirement, 89 enable or disable, 98 failback policy, 90 maintenance mode, 97 modify configuration, 98 on Applications tab, 103 primary interface, 90 progress report, 91 rehost, 95 view status, 98 Virtual SSAS Instance instance does not start, 122 Virtual SSAS instance add to Virtual SSAS, 92 delete, 99 enable or disable, 99 modify configuration, 99 monitor error, 104 monitoring, 94 on Applications tab, 103 optional components, 92 perfmon utility, 95 probe configuration, 93 revirtualize, 100 SQL Server Profiler, 94 Surface Area Configuration tool, 94 view status, 100 virtual data root, 92 Virtual SSAS Server drag and drop, 105 W websites HP, HP Subscriber's Choice for Business, 155 Windows authentication error,