This article is not part of the System Center Cloud series but we will use the final product to host System Center database instances.

Low-level design

Service accounts, user accounts and groups

Pre-create another set of service accounts that will be used for the new instance in the Active Directory. It is best practice to have separate accounts for each instance.

SQL DB Servers - Service accounts

  • sercontsqlfcic0dp0a
    • Service account: SQL Server Agent
    • Member Of
      • Domain Users
  • sercontsqlfcic0dp0d
    • Service account: SQL Server Database Services (Database Engine)
    • Member Of
      • Domain Users
  • sercontsqlfcic0dp0sr
    • Service account: Reporting Services
    • Member Of
      • Domain Users

Storage

  • You will need another cluster disks and Mount Point disk if you decide to use it.

Install another instance of Microsoft SQL Server on the first node of the Failover Cluster

The installation of the another clustered instance is similar to the installation process of the first instance.

  • New SQL Server failover cluster installation
  • Select same or different features.
  • Specify name of the new SQL Server cluster that will reside on this Windows Server 2012 R2 cluster.
      • contsqlfcic0dp0
  • Set name of the new instance and change the root directory if you want to separate OS and applications (SQL Server).
      • D:\Program Files\Microsoft SQL Server\
      • SCDPM0
  • Name of the SQL Server cluster resource group have to be different.
      • SQL Server (SCDPM0)
  • Set your new cluster disks or Mount Point disk if you decided to use it.
      • Previous Mount Point disk: The disk resource is already in use
  • Set IP address.
  • New service accounts.
      • SQL Server Agent: AD\sercontsqlfcic0dp0a
      • SQL Server Database Services (Database Engine): AD\sercontsqlfcic0dp0d
      • Reporting Services: AD\sercontsqlfcic0dp0sr
  • Paths will be different. Do not forget to set paths to another directory under the mount point as I explained in the previous article.
      • L:\SCDPM_Data\SQL\
  • Install

Configurations after installation

Configure dependencies in the Failover Cluster Manager

  • The process is the same. We need to set dependencies.

Install another instance of Microsoft SQL Server on the second node of the Failover Cluster

  • Same process like it was noted in the previous article.

Verify the installation

  • Same process like it was noted in the previous article.
« Previous Next »

Part of the series

  1. Building guest (virtual) Failover Cluster on Hyper-V host with Windows Server 2012 R2 - Part 1 - Create virtual machines
  2. Building guest (virtual) Failover Cluster on Hyper-V host with Windows Server 2012 R2 - Part 2 - Install and configure cluster
  3. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 1 - Design
  4. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 2 - Distributed Transaction Coordinator (MSDTC)
  5. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 3 - Configure storage and mount points
  6. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 4 - Install first node
  7. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 5 - Install second node
  8. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 7 - Manually configure Reporting Services