Posts

Linux Pacemaker Failover Clustering/SQL Server Firewall Access Rules

Firewall Ports: Linux Pacemaker Multi-Subnet Cluster for SQL Server Availability Groups Last updated: 2026-08-21 16:28:01 This document lists the firewall ports for a Linux Pacemaker Multi-Subnet Cluster that hosts SQL Server Availability Groups (AG). The ports are in order by function and by number, for the network and security teams. Contents Firewall Ports: Linux Pacemaker Multi-Subnet Cluster for SQL Server Availability Groups Contents 1. Pacemaker, Corosync, and Clustering Ports 2. SQL Server and Availability Group Ports 3. Custom and Non-Standard Port Examples 4. Research and Reference URLs 5. Document Notes Inter-node traffic: Allow every port in the tables below, Inbound and Outbound, between the cluster subnets. Note: The subnets 10.10.33.192/26 and 10.20.33.192/26 are examples. The actual IP ranges depend on your environment. 1. Pacemaker, Corosync, and Clustering Ports These ports keep quorum among the cluster nodes. The ports also s...

Cloud Recommendation - SQL Server Connection String Changes

Cloud Recommendation - SQL Server Connection String Changes Last updated: 2026-08-21 18:26:59 Table of Contents Overview Recommended Settings Availability Groups Failover .NET .NET Client Drivers .NET Connection Pooling .NET TLS Connectivity .NET ApplicationName/WorkstationID Java or Python Java or Python Client Drivers Java or Python Connection Pooling Java or Python TLS Connectivity Java or Python ApplicationName/WorkstationID Reference Links .NET References Java or Python References Shared References Overview This document recommends connection string changes for applications that connect to SQL Server with .NET, Java, or Python drivers. You can make these changes on-premises, before you migrate to a cloud infrastructure. These changes do not affect application performance. NOTE : Any changes must go through the SDLC first , before they go into production. Recommended Settings We recommend TRUE (or your driver's equivalent va...

Configuration Based SQL Server FCI Action On A Windows Server Failover Cluster

Configuration Based SQL Server FCI Action On A Windows Server Failover Cluster.md This document targets Windows Server 2022, Windows Server 2025, SQL Server 2022, and SQL Server 2025. This document presumes that you store your SQL Server installation media, service packs, configuration files, and scripts on a UNC path. Table of Contents Table of Contents Requirements Cluster Node First-Time Configuration SQL Server FCI Mount Point, Folder, and File Configuration SQL Server FCI Action: InstallFailoverCluster, AddNode, RemoveNode Windows Server 2025/SQL Server 2025 Notes Update Notes Requirements Before you install a SQL Server Failover Cluster Instance (FCI) on a Windows Server Failover Cluster (WSFC), review the Active Directory, DNS, and storage requirements. See Requirements for SQL Server AlwaysOn Feature on a Windows Server Failover Cluster.md . Cluster Node First-Time Configuration Use the steps below to configure a WSFC cluster node for first-time ...

Remote PowerShell Without “Second Hop” Problem

Remote PowerShell.md This document targets Windows Server 2022 and Windows Server 2025. Table of Contents Table of Contents Overview Windows Server 2022/2025 Administration Host and PowerShell Remote PowerShell Using CredSSP Reuse a Credential Across Multiple Sessions Remote PowerShell Using Resource-Based Kerberos Constrained Delegation Update Notes Overview Windows Server 2022 and Windows Server 2025 offer two server installation options : Server Core — This option is a minimal install. It removes the graphical shell and many nonessential components. You manage it from the command line, PowerShell, the Server Configuration tool (SConfig), or a remote tool. Server with Desktop Experience — This option installs the full graphical user interface and all client-experience features. You choose one option during setup. You cannot switch to the other option after installation, without a reinstall. If you manage a Server Core host, you see only a comm...