Remote onto node-1 with the SQL DVD inserted (or mounted), and Windows Failover Cluster already created with shared drives D, L, T, and S. (and ideally Z for backups, but not in this case).
Preperation
- Re-boot (if “access denied” end task “Service Host: DCOM Server Process Launcher (4)”)
- From Failover Cluster Manager run “validate cluster” (expect warnings for software level and only one network)
- Copy media to local drive (IE: SQL Server, CU, and maybe SSMS)
- Ensure you have service accounts for Engine and Agent.
- Take a screenshot of Windows uninstall screen – to aid possible uninstall
Run on each node individually
- Advanced
- Advanced cluster preparation
- Product Key, next
- Licence Terms, tic, next
- Microsoft Update, next
- Prepare Failover Cluster Rules (Windows Filewall Warning), next
- Feature Selection #1, [Database Engine Services]
- Feature Selection #2, root = [S:\]
- Instance Configuration, instance name, Instance ID
- Server Configuration, Agent and Engine (automatic), svc accounts, Grant perform VMT tasks
- Feature Configuration Rules, next
- Ready to Install, install
On Active Node
- Advanced
- Advanced cluster completion
- Cluster Node Configuration, Create AD name for instance
- Cluster Resource Group, next
- Cluster Disk Selection, tic all required disks (EG: D, L, T)
- Cluster Network Configuration, tic IPv4, untic DHCP, choose address within subnet (EG: 10.8.0.1)
- Server Configuration, next
Shared Settings
- Database Engine Configuration #1: sa pw, add current user, sql service account.
- Database Engine Configuration #2: Root = D:\, Data = D:\MSSQL, Log = L:\MSSQL, Backup = D:\Backup
- Database Engine Configuration #3 (tempdb): Data = T:\MSSQL, Log = L:\MSSQL
- Ready to Install, Install
Uninstall – if needed
- If it failed before “Advanced cluster completion” just remove from each node via Contol Panel.
- If it fails at the very end. You will need to run “Remove node from Cluster”, in the Maintenance tab of the media installation program.
Database Consultant 