Microsoft Licensing Primer
-
@BRRABill said:
From the MS definition:
Backup for Disaster Recovery provides additional licenses for servers used as offline (“cold”) backups, to help you recover in case of a catastrophic event. Cold backups help users regain access to critical data and applications following disasters and help protect the mission-critical solutions of your organization. For each server license you have with Software Assurance, you have the right to install the same software product on a “cold” backup server for disaster recovery.Cold is offline. Your description of how you intend to use Datto is not cold or offline.
-
I did a little further digging, and of course you are correct. I may have already mentioned this, but ML is now added to the short list (currently including only my wife) of people I just will in the future assume to always be right.
--
The Software Assurance benefit around cold server backup for disaster recovery includes the ability to install the server software, to configure it, to test disaster recovery procedures periodically, for example several times a year, and of course to move the backup server into production mode in the event of an actual disaster.
Other than this limited group of actions, cold server backups should be turned off. If they are turned on and used in any active mode, such as backup of production data, they are considered “warm” backups and should be licensed separately as any production server. As noted previously, warm backups are not included in this Software Assurance benefit.
-
But firing up to test is included in the SA benefits, that's good to know. So what the Datto does to see if a VM can fire up and sends a screenshot and immediately shuts down should be covered.
-
@scottalanmiller said:
But firing up to test is included in the SA benefits, that's good to know. So what the Datto does to see if a VM can fire up and sends a screenshot and immediately shuts down should be covered.
I would disagree, as what I also posted in that post says:
"If they are turned on and used in any active mode, such as backup of production data, they are considered “warm” backups and should be licensed separately as any production server." -
But the SA says: "includes the ability to install the server software, to configure it, to test disaster recovery procedures periodically"
-
@scottalanmiller said:
But firing up to test is included in the SA benefits, that's good to know. So what the Datto does to see if a VM can fire up and sends a screenshot and immediately shuts down should be covered.
Wow.. I agree with Scott here, It looks like as long as you have SA, you're covered for that that backup product does. Interesting.
-
@BRRABill said:
@scottalanmiller said:
But firing up to test is included in the SA benefits, that's good to know. So what the Datto does to see if a VM can fire up and sends a screenshot and immediately shuts down should be covered.
I would disagree, as what I also posted in that post says:
"If they are turned on and used in any active mode, such as backup of production data, they are considered “warm” backups and should be licensed separately as any production server."In my opinion you're not violating the license because you aren't firing up the VM to perform the backup, instead you are firing it up to confirm the backup. It's a subtle but important difference.
-
@Dashrender said:
Wow.. I agree with Scott here, It looks like as long as you have SA, you're covered for that that backup product does. Interesting.
Then how can you argue against:
"If they are turned on and used in any active mode, such as backup of production data, they are considered “warm” backups and should be licensed separately as any production server."Isn't the device backing up production data?
-
@BRRABill said:
@Dashrender said:
Wow.. I agree with Scott here, It looks like as long as you have SA, you're covered for that that backup product does. Interesting.
Then how can you argue against:
"If they are turned on and used in any active mode, such as backup of production data, they are considered “warm” backups and should be licensed separately as any production server."Isn't the device backing up production data?
At the moment that they are on, they are warm. When you turn them off, they are cold. The Microsoft terms that you quoted clearly state that cold backups are allowed and that you are allowed to have them warm momentarily to test with an SA license.
-
@BRRABill said:
Isn't the device backing up production data?
It's the warm vs. cold that we are discussing. That it is production isn't the concern here, we are assuming that it is all production.
-
@BRRABill said:
@Dashrender said:
Wow.. I agree with Scott here, It looks like as long as you have SA, you're covered for that that backup product does. Interesting.
Then how can you argue against:
"If they are turned on and used in any active mode, such as backup of production data, they are considered “warm” backups and should be licensed separately as any production server."Isn't the device backing up production data?
You are not backing up while it's warm, you do the backup before you make it warm. Therefore you're clear.
What they want to avoid is you spinning up a machine, using that machine itself to do the backup, then turning it off.. that would against the license.
-
I think they also set the "occasional" part of that to like a week or something.
Yet, if what you guys are saying is correct, then the Datto device should be OK if you have SA. Though I am not sure their daily screenshots would be OK.
@Chris can we get an official chime in on this?
-
@BRRABill said:
I think they also set the "occasional" part of that to like a week or something.
No, a week would be completely out of the question. They mean that once in a while you turn on a backup VM to see that the backup was good. That would be for minutes not for days.
-
@BRRABill said:
Yet, if what you guys are saying is correct, then the Datto device should be OK if you have SA. Though I am not sure their daily screenshots would be OK.
The Datto would be totally fine under SA. It is doing a momentary (literally just for a moment) and each one only once.
-
I meant a week in how often you were able to turn it on.
I read this on a SA right explanation, not from MS though.
"The DR server must normally be turned off except for one week every 90 days for software self-testing and patch management and during disaster recovery." -
@BRRABill ah okay, once every 90 days then. I'm very surprised that it is only that often. We'd have to get some clarification on the usable snapshot process. What they are describing is a full scale "running from it" DR test which is quite a bit different than we are talking about here.
-
I found the following on the Product Use document from November of 2015.
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.I can honestly admit I don't know what "within one week every 90 days" means.
-
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.
