How to deploy the SCSP server on a SQL SERVER 2008 cluster in ESXi

Article:TECH178076  |  Created: 2011-12-30  |  Updated: 2012-07-21  |  Article URL http://www.symantec.com/docs/TECH178076
Article Type
Technical Solution

Product(s)

Issue



Customer wants to deploy the SCSP server on a 2008 SQL SERVER cluster running on an ESXi Virtual Machine.


Environment



Windows server 2008 cluster

SQL server 2008 cluster

ESXi 4.0.x


Solution



Deploy the Windows Server 2008 Cluster in ESXi:

  1. The first step is to create a new vSwitch for the cluster heartbeat network, don’t assign any network adaptors to the switch as it’s going to be local only.
  2. Create a new virtual machine with a single hard disk. For the purposes of performance, suggest to assign 2 CPUs, 2GB RAM, 30GB drive for the OS, 1 vNIC in the default vSwitch0.
  3. Add a second vNIC and assign it to the cluster network vSwitch created in step 1.
  4. Install Windows Server 2008 R2 Enterprise and all the Windows Updates and named it. For example I  named it as SQLCluster01.
  5. Install the second Windows Server 2008 R2 Enterprise and named it as SQLCluster02.
  6. Create a disk for use as the Quorom, this needs to be shared and it must be “eagerzeroedthick” type. To do this, logon the ESCi by press ALT+F1 to enter the unsupported mode(Alt+F1, type unsupported and then your root password) and use the vmkfstools command to create it (vmkfstools –c <size> –d eagerzeroedthick –a lsilogic /vmfs/volumes/<datastore>/<folder>/<disk>.vmdk), for example: ~ # vmkfstools -c 1g -d eagerzeroedthick -a lsilogic /vmfs/volumes/datastore11/test_quorom.vmdk
    Creating disk '/vmfs/volumes/datastore1 (3)/test_quorom.vmdk' and zeroing it out...
    Create: 100% done.
  7. Add the new disk to SQLCluster01 using a new SCSI virtual controller (different from the current controller, e.g. the first HD of VM SQLCluster01 is on SCSI 0:1, You can set the Quorum to SCSI 1:0), achieve this progress by "edit the virtual machine settings" to add harddisk and tuning the corresponding controller to SCSI1:0 rather than default SCSI0:1 in  the vsphere client GUI. Also remembered to set the disk mode to independent-persistent.
  8. Check that the new SCSI controller is set to LSILogic and set the SCSI Bus Sharing to Virtual. To do this, logon the ESXi console again by press ALT+F1 to enter the unsupported mode(Alt+F1, type unsupported and then your root password) and edit .vmx file for current VM server, add the following lines under you just added SCSI controller:
    • scsi1:0.shared = "TRUE"            
    • scsi1.sharedBus = "virtual"
  9. Add the Quorum disk to the second virtual machine, using the same settings as previous steps.
  10. Then create other disks for some shared storage for the cluster too, it will be needed for the DTC application as well as the SQL server, to do it, referring step 6, then add the created HD to you VM`s SCSI1 controller. Confirm that the new SCSI controller is set to LSILogic and set the SCSI Bus Sharing to Virtual.
  11. Once the two VMs were booted, Be sure to do below things:
    • Mount and format the Quorum disk. In SQLCluster01, open the disk management snap-in and activate the new Quorum disk, create a new partition and format it to NTFS and mounted it as any letter which you want;
    • In SQLCluster02, activate the Quorum disk – it should pick up the partition and formatting automatically, then mounted it as E.
  12. Configure the Public Network. Asigning a static IP within the servers range, 1.1.1.0/24 for both servers. They have full network connectivity and rename to public.
  13. Configure the Private/Heartbeat Network. Assigning the IPs 192.168.255.44/24 and 192.168.255.55/24 to the Cluster Heartbeat Network Adaptors, and renamed it to private.\
  14. Join the domain. You have to build another VM and deployed as AD and added the DNS records in advance. Such as  A record of each host, A record of MSDTC and the A record of the virtual SQL instance and the Distributed Transaction Coordinator.
  15. Install Windows Failover Clustering on both nodes. Launch the “Add Features” wizard to install the Failover Clustering feature for each server.
  16. Configure the Cluster. Open the Failover Cluster Management console from Administrative Tools and run the “Validate a Configuration” wizard. Add both servers into the wizard and run all the defaults.
  17. Create the cluster. Run the “Create a Cluster…” wizard, select the servers as you did with the validation wizard, enter the cluster name and IP address that you created earlier in your DNS. Review the summary and create the cluster. The cluster service should automatically select the best disk for the quorum.
  18. Open the Failover Cluster Management console and right click Services and Applications and select “Configure a service or application”. Select the DTC and click next.
  19. Enter the DNS name you configured earlier for the DTC and the IP address you assigned and click next(DNS validation is necessary, so you must make all A records ready).
  20. Select the shared storage which assigned to the cluster, and click next.
  21. Complete the wizard and then verify the DTC is running by selecting it in the Services and Applications window, the Server Name, MSDTC and Drive should all presented as online

Once the Windows cluster deployed, the following process it to install the SQL server cluster, some pre-requisite for SQL server 2008:

  • Windows 2008 Cluster
  • .Net Framework 3.5 SP1
  • Domain Members

To install the SQLServer 2008 cluster,

  1. Open your SQL Server 2008 installation media, select a “New SQL Server failover cluster installation”.
  2. Click through the wizard, enter key and license info and install the Setup Support Files. Check and resolve any issues in the setup support rules.
  3. Select the features that you require
  4. Configure the SQL Server Network Name which created earlier in the DNS records and  installing the default instance of SQL.
  5. Check the disk space requirements are OK and click next. Click next to create a new Cluster Resource Group for SQL.
  6. Select the available cluster disk and click next.
  7. Input the network address which configured earlier for the SQL Cluster
  8. In the Cluster Security Policy dialog box, accept the default value of Use service SIDs (Microsoft’s recommended option). Configure your service accounts and collation, DB Engine Authentication and Data Directories.
  9. After that, go through to your installation and complete.
  10. Verify all the resources required for the cluster application are available in the Failover Cluster Management console.
  11. Once all set up, then try to install the second cluster node. Run the SQL 2008 installer and select the “Add node to a SQL Server failover cluster” option. As before, go through the setup support rules, check the Cluster Node Configuration, configure the Service Accounts, step through the verifications and install the node.
  12. If it all completed successfully, you now have a working Windows Server 2008 Cluster with an active/passive SQL 2008 database cluster, running on a single ESXi 4 Server.

Deploy the SCSP Server on a SQLServer 2008 Cluster

  1. Download the latest release of SCSP(later than v5.2.7)
  2. Go through the installation wizard till to choose the database
  3. Input the Virtual IP address of the SQLServer Cluster 2008(the VIP of SQL`s DTC)
  4. Keep the instance as blank in this environment then next
  5. When the wizard prompts to input the password of scspdba, be sure to input the password with correct format.
    Password must:
    - be 8 to 18 characters long
    - contain only letters, numbers, #, and _
    - not begin with _
    - contain at least two non-letter characters

If the whole procedure done as expected, then the SCSP server could communicate with the SQL SERVER 2008 cluster with high available and redundancy.




Article URL http://www.symantec.com/docs/TECH178076


Terms of use for this information are found in Legal Notices