ReleaseBytes
aws Modernizing with AWS Blog ·

Guide to Migrating SQL Server FCI Storage to FSx for NetApp ONTAP Gen 2

blogdataawsengineeraws-ec2
announcement

This post details a step-by-step procedure for migrating SQL Server Always On Failover Cluster Instance (FCI) storage from Amazon FSx for NetApp ONTAP Gen 1 to Gen 2. It addresses the unique challenges of iSCSI block storage for SQL Server, aiming for zero data loss and a minimal maintenance window. The guide leverages NetApp SnapMirror, covering how to quiesce SQL Server, reconfigure iSCSI on cluster nodes, and bring the FCI back online. Users can expect an estimated downtime of 30-60 minutes with proper preparation.

  • →Migration Challenges for SQL Server FCI Storage
  • →SQL Server FCI Migration Architecture Overview
  • →Prerequisites for FCI Storage Migration
  • →Phase 1: Establish SnapMirror Replication
  • →Phase 2: Cutover and Maintenance Window Procedure
Notes (5) ›
  • Migration Challenges for SQL Server FCI Storage

    The article outlines the specific difficulties in migrating iSCSI block storage for SQL Server Always On Failover Cluster Instances (FCI) on Amazon EC2 using Amazon FSx for NetApp ONTAP. It highlights constraints such as SQL Server's exclusive file access, WSFC cluster recognition of new disks, and MPIO reconfiguration across all nodes.

  • SQL Server FCI Migration Architecture Overview

    A reference architecture is presented for migrating SQL Server FCI storage between Gen 1 and Gen 2 FSx for ONTAP file systems within the same VPC and across two Availability Zones. Key components include AWS Managed Microsoft AD, EC2-based WSFC cluster nodes, Gen 1 and Gen 2 FSx for ONTAP, SnapMirror replication, and iSCSI with MPIO.

  • Prerequisites for FCI Storage Migration

    Before beginning the migration, users must ensure they have access to the SQL Server FCI, the NetApp ONTAP SVM CLI, and each WSFC node. Prerequisites also include pre-creating igroups on the Gen 2 SVM, scheduling a maintenance window (estimated 30-60 minutes), and documenting a rollback plan.

  • Phase 1: Establish SnapMirror Replication

    The first phase involves setting up SnapMirror replication between the Gen 1 source and Gen 2 destination FSx for ONTAP file systems. This includes creating destination DP volumes, recording inter-cluster LIFs, establishing cluster and SVM peering, and initializing scheduled incremental updates, ensuring the destination is nearly in sync with the source.

  • Phase 2: Cutover and Maintenance Window Procedure

    This critical phase details the step-by-step cutover procedure. It begins with quiescing SQL Server databases to prevent new connections, stopping the FCI role to release shared disk resources, and performing a final SnapMirror sync and break on the ONTAP Gen 2 file system.

Read the original announcement →

https://aws.amazon.com/blogs/modernizing-with-aws/migrating-sql-server-fci-storage-from-amazon-fsx-for-netapp-ontap-gen-1-to-gen-2/

Related releases