Dell APEX Block Storage for Public Cloud: Microsoft SQL Server Multi-Subnet Failover Clustering Deployment

• 1

  Executive summary

• 1

  Introduction
• 2

  Revisions
• 3

  Audience
• 4

  Terminology
• 5

  We value your feedback

• 1

  Dell APEX Block Storage for Public Cloud
  • How can we achieve this?
• 2

  TCO considerations
• 3

  SLA reimagined
• 4

  Unique multi-AZ durability
• 5

  Resourceful workload placement
• 6

  Dell APEX Block Storage for Public Cloud architecture
• 7

  Dell APEX Block Storage components
• 8

  Architecture
• 9

  Metadata communication
• 10

  Regions and availability zones
• 11

  APEX Public Cloud delivers

• 1

  Microsoft SQL Server 2022 multisubnet failover cluster on Dell APEX Block Storage for Public Cloud
• 2

  Network architecture
• 3

  Logical architecture

• 1

  Overview
  • Overview
• 2

  Install Windows failover cluster roles and features
• 3

  Install Dell APEX Block Storage SDC
  • Provision APEX Block Storage volume
  • Map the volumes to the Windows host
  • Initialize and format the Disks

• 1

  Failover cluster validation wizard
• 2

  Install Windows Server 2022 multi-subnet cluster

• 1

  Install SQL Server 2022
• 2

  Adding a second SQL Server 2022 node to the cluster
• 3

  Adding a third SQL Server node on a SQL Server 2022 multi-subnet cluster
• 4

  Validate SQL Server 2022 multi-subnet failover cluster functionality

• 1

  Testing and validation
• 2

  Single SQL Server 2022 database instance in a single AWS AZ
• 3

  Linear scaling of SQL Server 2022 database instances across multi-AZs

• 1

  Best practices
• 2

  Dell APEX Block Storage for Public Cloud
• 3

  SQL Server database on AWS
• 4

  SQL Server database tuning considerations

• 1

  Conclusion

• 1

  APEX Block Storage SDS instance using Amazon instance store
• 2

  APEX Block Storage SDC instance using Amazon instance store
• 3

  APEX Block Storage gateway and presentation server
• 4

  HammerDB Instances

• 1

  Dell APEX Block Storage for Public Cloud documentation