Post reply

Clustering on different subnets with AlwaysOn added on the top of it.

  • December 3, 2013 at 8:49 pm

    #287090

    All SQL Guru's:

    We are setting up a DR solution on Windows 2008R2 and SQL 2012. There are 2 sub-nets (one at each site - Prod and DR) and total four nodes (2 each on each sites (each site having one SQL Server Instance)).

    Node 1 and 2 in SUBNET A , Node 3 and 4 in Subnet B. (Node 1 and 2 has SQL cluster instance, Node 3 and Node 4 has DR cluster instance).

    Now AlwaysOn availablity group on Subnet A and Subnet B needs to be setup so that we dont need to change the IPs in case of Site failure.

    Question:

    1) On which subnet we assign the virtual IP (Subnet A OR B). How will one know if the other is down? more insight on this will be appreciated.

    2) Do i need different storage replication (SAN replication) if the underlying storage on the Site A goes down?

    Thanks

  • December 3, 2013 at 10:34 pm

    #1670585

    I have just completed a very similar build - Windows 2012 R2 Core and SQL Server 2012.

    What you want to do is to add a listener across Multiple Sub-nets:

    1.With SSMS object explorer open; drill down into AlwaysOn High Availability –> Availability Groups –> “your AG name”.

    2. Right click on Availability Group Listeners and select Add Listener.

    3. Set the Listener DNS Name (15 Character Limit)

    4. Set Port to anything you want noting that this is the port your application connection strings will have to use.

    5. Set Network Mode to Static IP.

    6. Click Add to add a new IP address to the listener (a minimum of one is required but in our architecture you would need two, one per subnet).

    7. Select the appropriate subnet from the drop down box.

    8. Enter your IPv4 static IP address and click OK.

    9.Repeat steps 6-8 for each subnet in the cluster.

    10. Click OK to create your new AG listener.

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

  • December 3, 2013 at 10:47 pm

    #1670586

    Thanks for this.

    One more question. Though silly one. Can i install another instance on the subnet B (for PRE-PROD and one installed previously was DR (on Subnet B)) and include that in AG? I think, the answer is NO. Only one Instance per FCI?

    My requirment is to have a PRE-PROD and i want that to accomodate in 4 nodes (in total). Can i do that?

    Please clarify.

    Thanks

  • December 3, 2013 at 11:03 pm

    #1670588

    So you want your pre-production environment to exist on your production environment ? Why ?

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

  • December 3, 2013 at 11:07 pm

    #1670589

    No, Not on PROD but on DR (Subnet B) [Subnet B= DR + PRE-PROD]

  • December 3, 2013 at 11:12 pm

    #1670590

    Okay, I just see DR as part of production.

    You can install a second instance on the DR site (and not part of the DR SQL Cluster) and as long as it is part of the Windows cluster that your original Available group is part of you can add the Available group to that instance.

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

  • December 3, 2013 at 11:19 pm

    #1670591

    Thanks a ton. It helps.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply