May 10, 2018 at 10:11 am
Hello,
We got a requirement for setting up AlwaysOn for SkypeForBusiness physical servers in our environment. And they are referring to this link
https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-high-availability-and-disaster-recovery/alwayson-availability-group
SfB were mentioning that they need AlwaysOn Active/Passive cluster. So, is this the Active Databases on Primary Node and Non-Readable DB's on Secondary? Or is it AlwaysOn Failover Cluster Instance (FCI) ?
Should we call non-readable secondary DB as Passive Node? What about licensing, is is only for 1 single/active node? Or should we buy bill the SfB team for licences on both the nodes? All our SQL VM's are in a ESX host?
If it is a AlwaysOn Active/Passive...then what is the benefit over AlwaysOn FCI?
Please help me understanding this...
May 10, 2018 at 12:55 pm
dan.brown1 - Thursday, May 10, 2018 10:11 AMHello,We got a requirement for setting up AlwaysOn for SkypeForBusiness physical servers in our environment. And they are referring to this link
https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-high-availability-and-disaster-recovery/alwayson-availability-groupSfB were mentioning that they need AlwaysOn Active/Passive cluster. So, is this the Active Databases on Primary Node and Non-Readable DB's on Secondary? Or is it AlwaysOn Failover Cluster Instance (FCI) ?
Should we call non-readable secondary DB as Passive Node? What about licensing, is is only for 1 single/active node? Or should we buy bill the SfB team for licences on both the nodes? All our SQL VM's are in a ESX host?
If it is a AlwaysOn Active/Passive...then what is the benefit over AlwaysOn FCI?
Please help me understanding this...
You are completely confused.
Always on contains a primary and any number of secondaries. The secondaries can be read-only, and can be synchronous or asynchronous.
Clustering can be configured as an active/passive configuration.
Prior to setting up Always On, a cluster does need to be created. Always On is based upon clustering technologies.
If there is a single database, without a read-only, you can use standard edition. If there are more than one database(s), then you will need standard edition.
The main difference between an availability group and clustering is shared storage. Clustering shares the storage, always on maintains 2 copies of the database on different storage.
This is a good series of articles on the subject. I suggest you read these first.
http://www.sqlservercentral.com/stairway/112556/
If the secondary is read only, you will need to license both the primary and secondary. If the secondary is not read only, then it will only need software assurance. This is the same as an active/passive cluster.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
May 11, 2018 at 3:52 am
dan.brown1 - Thursday, May 10, 2018 10:11 AMHello,We got a requirement for setting up AlwaysOn for SkypeForBusiness physical servers in our environment. And they are referring to this link
https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-high-availability-and-disaster-recovery/alwayson-availability-groupSfB were mentioning that they need AlwaysOn Active/Passive cluster. So, is this the Active Databases on Primary Node and Non-Readable DB's on Secondary? Or is it AlwaysOn Failover Cluster Instance (FCI) ?
Should we call non-readable secondary DB as Passive Node? What about licensing, is is only for 1 single/active node? Or should we buy bill the SfB team for licences on both the nodes? All our SQL VM's are in a ESX host?
If it is a AlwaysOn Active/Passive...then what is the benefit over AlwaysOn FCI?
Please help me understanding this...
In the organisation I work at we used FCIs for our skype implementation not AGs.
As already mentioned, AlwaysOn is the re branded high availability technology and incorporates FCIs and\or Availability Groups.
Active\passive are not really terms that are used anymore under Windows Server Failover Clusters.
Read my stairway to AlwaysOn starting at this link
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 26, 2018 at 5:38 am
Yes. We did installed FCI for SfB. However, as they are insisting for dedicated storage and local drives, removed FCI and we had to configure High Safety DB mirroring on Standard Edition 2014 servers with witness on a express edition server.
May 29, 2018 at 10:09 pm
One correction from the second post.
Standard Edition - Basic Availability Group with one database only
Enterprise Edition - Availability Groups with multiple databases.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply