Sunday, July 16, 2017

SQL Server 2016 AG Setup Part 5–AG2 between SQL01\AGINST2 and SQL02\AGINST2

During this example, same port has been used for as part of illustration. Different port number between AG and instance is not a requirement, it’s a best practice instead as one instance can support multiple AG groups.
InkedVirtualBox_PEGAAD_15_07_2017_15_03_22_LI

VirtualBox_PEGAAD_15_07_2017_15_03_29

VirtualBox_PEGAAD_15_07_2017_15_04_01

Important point: Since we already have AG1 running with different SQL instances on port 5022, we need to choose different port here to avoid conflict.
VirtualBox_PEGAAD_15_07_2017_15_05_56

VirtualBox_PEGAAD_15_07_2017_15_04_18
VirtualBox_PEGAAD_15_07_2017_15_04_46
VirtualBox_PEGAAD_15_07_2017_15_04_55
VirtualBox_PEGAAD_15_07_2017_15_05_02
VirtualBox_PEGAAD_15_07_2017_15_06_08
VirtualBox_PEGAAD_15_07_2017_15_07_15

Make sure SQL01\AGINST2 and SQL02\AGINST2 only listen on specific IP, instead of “LISTEN ALL”, that will block AG Listener binding to same port.
VirtualBox_SQL01_15_07_2017_15_15_37


VirtualBox_SQL01_15_07_2017_15_15_32

VirtualBox_SQL01_15_07_2017_15_18_38
VirtualBox_SQL01_15_07_2017_15_30_10

Otherwise connection to AG Listener won’t be successfully.
VirtualBox_PEGAAD_15_07_2017_15_11_33

VirtualBox_SQL01_15_07_2017_15_11_23