LLI Wiki — My Digital Knowledge Base

SQL Server: new cluster design checklist

Checklist to prepare a SQL Server failover cluster or availability group: AD, network, accounts, storage, instance.

Use this checklist to prepare the design of a new SQL Server cluster (failover cluster instance and/or Always On availability group) before requesting the infrastructure. The values below are examples to adapt; items marked "to define" must be settled with the system, network and security teams.

General

Item Example / question to ask
SQL Server version SQL Server 2017 Standard
Number of replicas 2
Location Same site, on different ESX hosts
Estimated number, size and activity of databases To define

Active Directory

Network

Item Detail
Subnets Public network and private (heartbeat / cluster) network
IP addresses One IP dedicated to the failover cluster; one IP per availability group listener
Listener name Common prefix defined by the naming convention (for example lsn_)
Listener port One port per listener, within a reserved range (for example 15000 to 15010)
Endpoint port One port per endpoint, 5022 by default
Heartbeat Dedicated VLAN with fixed IPs, to improve cluster stability
DNS Decide whether a DNS alias is needed

Service accounts

To prepare before installation:

Servers

Item Example
CPU / RAM 8 vCPU / 64 GB
Virtual SCSI adapters 2
Virtual network adapters 2

On every node:

Failover cluster

Storage

Role Letter Format / remark Size (example)
System (OS) C: GPT 100 GB
Databases G: GPT, 64 KB allocation unit 200 GB
System databases S: GPT, 64 KB allocation unit 40 GB
tempdb T: GPT, SSD preferred 40 GB
Transaction logs L: GPT, 64 KB allocation unit 60 GB

Check with the system administrator that volumes can be extended online (both at OS and hypervisor level).

Backup

Instance

SSIS server (if separate)

Item Example
CPU / RAM 4 vCPU / 8 GB
Storage C: and D:, 80 GB each
Note Install only the SSIS engine, with a local database

Items to document

Mastodon LLIMastodon SocialFosstodon