High availability without shared stores technique?

  • Hi,

    We have 2 physical box and installed WIN 2008 R2 and SQL 2014 enterprise editions. Not yet created database name and other configurations.

    Which is best solutions to be choose for database High availability with Virtual IPs?

    Is there new method available in SQL 2014 version? without using shared storage and common virtual IP.

    Generally 2 node cluster attached to storage, two public IP, private IPs and one virtual IPs.

    Thanks

    ananda

  • options without shared storage are

    traditional database mirroring (requires at least std edition of sql server)

    AlwaysOn groups (requires at least enterprise edition of sql server)

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Thanks for reply..

    Database mirroring configuration involved in two different IP address for two servers.

    Is it possible for one common virtual IP in always on group?

  • to use one common virtual IP, AlwaysOn group with a listener is the only option

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Thank you Mr. Perry.

    Could you Pl. provide links or any document for how to configure listener in always on group?

  • SQL Galaxy (11/17/2014)


    Thank you Mr. Perry.

    Could you Pl. provide links or any document for how to configure listener in always on group?

    Do you know how to deploy an AlwaysOn group and the infrastructure it requires?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Perry Whittle (11/17/2014)


    SQL Galaxy (11/17/2014)


    Thank you Mr. Perry.

    Could you Pl. provide links or any document for how to configure listener in always on group?

    Do you know how to deploy an AlwaysOn group and the infrastructure it requires?

    Hi Perry, I have as following setup for prerequisite's to deploy an AlwaysOn group configurations.

    1. Two HyperV (virtual) server with windows 2008 R2 64 bit version

    2. These two servers joined member of domain.

    2. Installed SQL2012 enterprise edition version each HV servers.

    3. one domain id for SQL server service account setup. (Does network service account can able to configure AlwaysOn group?)

    Does Application connect to common virtual IP for an AlwaysOn groups? am I Correct?

    Thanks

    ananda

  • You've missed out very important steps and all of this is required before you even get to creating and configuring a listener. This is still at a very high level, you need to look deeper into the requirements. I've re numbered your steps and inserted new ones 😉

    SQL Galaxy (11/17/2014)


    1. Two HyperV (virtual) server with windows 2008 R2 64 bit version

    2. These two servers joined member of domain.

    3. Create a Windows Server Failover Cluster across the 2 nodes

    4. Installed SQL2012 enterprise edition version each HV servers.

    5. Enable each instance via SQL Server configuration manager to support AlwaysOn groups

    What witness type do you intend to use for your Windows Server failover Cluster?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Thank you for mention missed points(number), I have updated my documents.

    What witness type do you intend to use for your Windows Server failover Cluster?

    It means FULL RECOVERY MODE. For data synchronize both database, but I am not sure.

    I have one domain account for SQL service account for both nodes, there is no special privileges assigned just for service account.

    Does it require any special privileges for domain service accounts?

  • SQL Galaxy (11/18/2014)


    What witness type do you intend to use for your Windows Server failover Cluster?

    It means FULL RECOVERY MODE. For data synchronize both database, but I am not sure.

    Witness for quorum, not database recovery model (which has to be full recovery model for availability groups). You may want to do some reading on Availability Groups quorum (and AGs in general) to understand why you need a witness in this case and what the options are.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • SQL Galaxy (11/18/2014)


    Thank you for mention missed points(number), I have updated my documents.

    No, they are still a very high level, you need to be looking a lot deeper into this. It will pay you to study Windows Server Failover Clusters and AlwaysOn Availability groups in a lot more detail. Start by reading my stairway series on this site, the first 3 levels are linked below

    Level1[/url]

    Level2[/url]

    Level3[/url]

    Also have a read through this

    AlwaysOn Groups[/url]

    SQL Galaxy (11/18/2014)


    Perry Whittle


    What witness type do you intend to use for your Windows Server failover Cluster?

    It means FULL RECOVERY MODE. For data synchronize both database, but I am not sure.

    No, it's nothing to do with the database recovery model, it's a fundamental part of the Windows Server Failover Cluster configuration and is nothing to do with SQL Server.

    Read the above for more detail.

    SQL Galaxy (11/18/2014)


    I have one domain account for SQL service account for both nodes, there is no special privileges assigned just for service account.

    Does it require any special privileges for domain service accounts?

    Yes, due to the way Service Principal Names work, if you want the SPN to be created successfully upon failover, all replicas in the AlwaysOn Availability group must use the same service account. This is because an SPN is registered against the user account, if the instances use different accounts the SPN will fail when the listener is passed to nodes where instances use a different service account.

    The accounts require no special privileges, they are granted during installation.

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 11 posts - 1 through 10 (of 10 total)

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