June 22, 2018 at 4:15 am
Hi, just wondering what the situation is re licensing with Basic availability groups in the event of a failover ?
I understand that with SA you have mobility rights, but as each BAG can only contain one database, what happens in the event of a failover of one (Of Four) databases ?
So we then end up with the active node running three of our database, and the formerly passive node running the fourth one.
Admittedly its a bit of a semantic argument, and I think the answer is that you sort out the problem DB and move it back to the active node, then say no more about it. However, it does seem that you are basically given an opportunity to hang yourself out to dry licensing wise.
Is there anything in the licensing that covers this scenario ?
We are very keen to always be compliant in all matters regarding licensing, hence why this makes us a little uncomfortable, also complicated by the fact that all our instances have a small admin database that standardises settings, jobs and provides alerting, would that count as serving data ? it would be the same as running MS or 3rd party admin tools ?
My thinking is that we take it seriously and are following the spirit of the licensing agreement but these small issues could trip us up.
Giot a meeting to discuss with a licensing expert next week but want to have it straight in my head.
July 5, 2018 at 4:45 am
mark 52160 - Friday, June 22, 2018 4:15 AMHi, just wondering what the situation is re licensing with Basic availability groups in the event of a failover ?I understand that with SA you have mobility rights, but as each BAG can only contain one database, what happens in the event of a failover of one (Of Four) databases ?
So we then end up with the active node running three of our database, and the formerly passive node running the fourth one.
Admittedly its a bit of a semantic argument, and I think the answer is that you sort out the problem DB and move it back to the active node, then say no more about it. However, it does seem that you are basically given an opportunity to hang yourself out to dry licensing wise.
Is there anything in the licensing that covers this scenario ?
We are very keen to always be compliant in all matters regarding licensing, hence why this makes us a little uncomfortable, also complicated by the fact that all our instances have a small admin database that standardises settings, jobs and provides alerting, would that count as serving data ? it would be the same as running MS or 3rd party admin tools ?
My thinking is that we take it seriously and are following the spirit of the licensing agreement but these small issues could trip us up.
Giot a meeting to discuss with a licensing expert next week but want to have it straight in my head.
Basic AGs are what they say, no readable secondary and a one to one database relationship.
It's a replacement option for the deprecated database mirroring feature
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 5, 2018 at 9:39 am
I think you're right, in that you need SA and you get one failover. You'd be OK with the licensing here. We have BAGs here, but we assume that failover is all 4 (or 5) or none. If one moved, we'd probably just move all of them.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply