SQL Server Migration Plan-Always On Availability
SQL Server Migration Plan-Always On Availability
As per our initial discusstion, we need to migrate the existing SQL Server into Nutanix Environment with Always on
high availability Configuration.
Phase 1:
• Node Names
• Listener Name(s)
• User Database to Listener Mappings
• Instance Names ( if not default )
• Port SQL / Listener/ Mirroring (If not default)
• Always on configuration mode AG(Synchronization or Asynchronization)
• Preferred replica for Availability Group
• Multi Subnet Platform / Single Subnet Platform
• List of database sizes in each SQL Server
• Service Account Details
• Is it involved SQL server version upgradation is required?
• Backup schedule and retention periods?
• Preferred time to run the database maintenance( Index/ Statics/database integrity)
• Secondary replica is readable state\ standby.
Phase 2:
Once we have the above information, will move forward and connect with your team through WebEx call, we
request to show the existing environments and we will note down the key points and do the Analysis, then we will
submit complete plan of action for database migration.
A quick summary of road map steps which will carry through migration listed below
• Required two new machines (number increases depends upon the replicas)
• Server\Wintel Team will install the Operating System and WSFC cluster
• DBA will take care of the SQL Server (2012/2014/2016/2017) installation
• Implement best practices related to security
• Database Migration \ upgradation
• Configure the Always on high availability
• Configure maintenance Plans
• Test failover and failback Capability
• Application connectivity checking and signoff
• Handover to client
1
Provisioning 3 node Always on availability Architecture
Windows prerequisites
1. Ensure that each computer is running on 64 BIT Windows 2012 R2
2. Ensure that the WSFC cluster contains sufficient nodes to support your availability group
3. Ensure that all applicable Window hotfixes installed on every node in the WSFC cluster.
4. Failover Cluster Feature is installed on all machines
5. Administrative Accounts have been created
• Domain Administrator to perform install
• SQL Server Account
• SQL Agent Account
6. Storage has been allocated and assigned as follows:
• 5 disks for SQL Database storage (2- MDF, 1- LDF, 1-TempDB, 1-SQL Server Root)
• 1 drive for OS server
7. IP Address reserved for AG Listener
8. Temporary File Share accessible by SQL Service Account and both Servers
Details Information we collect during the WebEx call for analysis purpose
• Server name :
• IP Address :
• SQL Server Version(Standard/Enterprise) :
2
• Port number(Default:) : 1433
• SQL Server Patch :
• SQL Server Feature Installation
• Database Engine Services
• SQL Server Replication
• Full-Text and Semantic Extractions for Search
• Data Quality Services
• Analysis Services
• Instance(Default/Named) :
• Service Account Details :
• Server Configuration:
• Authentication Mode
• Windows Authentication mode
• Mixed Mode (Windows and SQL)
• Specify SQL Server Administrators
• Data Directories
• Data Root Directories :E:\MSSQL
• System database Directories :E:\MSSQL\MSSQL11.MSSQLSERVER\MSSQL\DATA
• User Database Directories: \MSSQL\Data
• User Database Log Directories :\MSSQL\Log
• Temp DB Directory:\MSSQL\Tempdb
• Temp DB Log Directory:\MSSQL\Tempdb
• Backup Directory:E:\MSSQL\Backup
• Collation:
• Database Engine:SQL_Latin1_General_CP1_CI_AS
• Analysis Services: Latin1_General_CI_AS
• Network Software
• Share Memory :Enabled
3
• Named Pipes: Enabled
• TCP/IP :Enabled
• VIA : Disabled
• SP_configure settings
• backup compression default
• max degree of parallelism
• min server memory (MB)
• max server memory (MB)
• remote admin connections
• remote query timeout (s)
• Database Mail XPs
• SMTP address