Microsoft Licensing Primer
-
Here is the rest of it...
In order to use the software under disaster recovery rights, Customer must comply with the following terms:
• The OSE on the disaster recovery Server must not be running at any other times except as above.
• The OSE on the disaster recovery Server may not be in the same cluster as the production Server.
• Other than backup instances run on Microsoft Azure Services, Windows Server License is not required for the disaster recovery Server if the following conditions are met:
o The Hyper-V role within Windows Server is used to replicate Virtual OSEs from the production Server at a primary site to a disaster recovery Server.
o The disaster recovery Server may be used only to- run hardware virtualization software, such as Hyper-V,
- provide hardware virtualization services,
- run software agents to manage the hardware virtualization software,
- serve as a destination for replication,
- receive replicated Virtual OSEs, test failover,
- await failover of the Virtual OSEs, and
- run disaster recovery workloads as described above.
o The disaster recovery Server may not be used as a production Server.
• Use of the software backup Instance should comply with the License Terms for the software.
• Once the disaster recovery process is complete and the production Server is recovered, the backup Instance must not be running at any other times except those times allowed here.
• Maintain SA coverage for all CALs, External Connector licenses and Server Management Licenses under which it accesses the backup instance and manage the OSEs in which that software runs.
• Customer’s right to run the backup Instances ends when Customer’s Software Assurance coverage ends.
-
Also, does this ...
Maintain SA coverage for all CALs, External Connector licenses and Server Management Licenses under which it accesses the backup instance and manage the OSEs in which that software runs.
Mean that you need SA on the CALs as well?
So say I have a Server 2012 VL with 20 2012 CALs to access it.
I need SA on both the server AND the CALs?
-
Technically only on the CALs used during the DR test.
-
@scottalanmiller said:
Technically only on the CALs used during the DR test.
But why would you need any CALs at all for that? Or maybe 1 if anything?
-
@BRRABill said:
• For brief periods of disaster recovery testing within one week every 90 days;
And do you have a guess as to what
"• For brief periods of disaster recovery testing within one week every 90 days;"
means? -
@BRRABill said:
@BRRABill said:
• For brief periods of disaster recovery testing within one week every 90 days;
And do you have a guess as to what
"• For brief periods of disaster recovery testing within one week every 90 days;"
means?It means you can spin up your DR site to make sure everything works. for small amounts of time not to exceed a max of one week every 90 days.
-
@JaredBusch said:
It means you can spin up your DR site to make sure everything works. for small amounts of time not to exceed a max of one week every 90 days.
So I could spin up for an hour every day for 90 days. That's less than 1 total week.
-
@BRRABill said:
@JaredBusch said:
It means you can spin up your DR site to make sure everything works. for small amounts of time not to exceed a max of one week every 90 days.
So I could spin up for an hour every day for 90 days. That's less than 1 total week.
No.
-
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
-
@BRRABill said:
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
Yes. That is what it means.
-
Since it is December and hopefully e-mails from ML are flowing again, let's see if we can get an official chime in from @Chris .
-
@JaredBusch said:
@BRRABill said:
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
Yes. That is what it means.
I called MS to confirm this today.
You were 100% right.
Once every 90 days, and only with SA.
-
@BRRABill said:
@JaredBusch said:
@BRRABill said:
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
Yes. That is what it means.
I called MS to confirm this today.
You were 100% right.
Once every 90 days, and only with SA.
No SA is required for this per our MS rep. Though all we do spin them up with no network connection and the shut them right back down. Once per quarter.
-
@Jason said:
No SA is required for this per our MS rep. Though all we do spin them up with no network connection and the shut them right back down. Once per quarter.
You might want to check on that.
It's only allowed once every 90 days WITH SA.
-
@BRRABill said:
@Jason said:
No SA is required for this per our MS rep. Though all we do spin them up with no network connection and the shut them right back down. Once per quarter.
You might want to check on that.
It's only allowed once every 90 days WITH SA.
That's not what our EA Rep says. We have checked on it many times.
-
I believe you are referring to cold/standby licensed backup servers. Which is a right under SA's standby server rights but that is highly different then making sure a live backup boots and then turning it back off, there is no 90 day restriction either, if you have SA you can also use Standby servers.
Also if you have Azure for your DR site then you don't need anything. All windows base licensing is covered.
-
@Jason said:
I believe you are referring to cold/standby licensed backup servers. Which is a right under SA's standby server rights but that is highly different then making sure a live backup boots and then turning it back off, there is no 90 day restriction either, if you have SA you can also use Standby servers.
Also if you have Azure for your DR site then you don't need anything. All windows base licensing is covered.
What do you mean a "live backup" ... if you boot a copy of server up for 1 second you need another license for it. MS has no disaster recivery rights.
With SA, you can boot it once every 90 days.
@scottalanmiller I am sure will chime in here to support this...
-
A bit offtop:
Isn`t MS is the only company who has certification program for its licensing? -
@BRRABill said:
@Jason said:
I believe you are referring to cold/standby licensed backup servers. Which is a right under SA's standby server rights but that is highly different then making sure a live backup boots and then turning it back off, there is no 90 day restriction either, if you have SA you can also use Standby servers.
Also if you have Azure for your DR site then you don't need anything. All windows base licensing is covered.
What do you mean a "live backup" ... if you boot a copy of server up for 1 second you need another license for it. MS has no disaster recivery rights.
With SA, you can boot it once every 90 days.
@scottalanmiller I am sure will chime in here to support this...
That's not true. SA is what gives you disaster recovery rights and you can keep this live backup DR running as a cold site as long as it's not being actively being used for production.
We're on Enterpise so we don't need SA to test backups, but you do need SA for Diaster recovery on other hardware and no you do not need a second windows license for a replicated DR copy.
-
@Jason said:
That's not true. SA is what gives you disaster recovery rights and you can keep this live backup DR running as a cold site as long as it's not being actively being used for production.
That is what the whole latest discussion was about. That the usage rights for SA state:
The backup Instance can run only during the following exception periods:
• For brief periods of disaster recovery testing within one week every 90 days;
• During a disaster, while the production Server being recovered is down; and
• Around the time of a disaster, for a brief period, to assist in the transfer between the primary production server and the disaster recovery Server.
