Disaster Recovery - Hosted Server
-
@Dashrender said:
@thecreativeone91 said:
Easy, Do 4 hr or less on site service contract (both dell and cisco do 2 & 4 hr).
The have baremetal backups.This only promised that they will be at your door in 2 or 4 hours.. not fixed in that timeframe!
True. Especially with Dell. With Cisco SmartNet OnSite if you have either servers or networking devices you can have them backed up to the cloud (as well as local) and Cisco will just have someone their with a replacement unit in 2hrs and will reload the config from backups.
-
@Breffni-Potter said:
What if you could keep the Azure VM off as a disaster box, power it on, restore from backup, would be much cheaper long term if you only paid for Azure storage rather than have it on 24/7 then if a disaster does strike you can use it.
Can you? Yes. How much will you save? Some. Is it worth it? I doubt it. I'd put this as getting pretty close to silly in terms of cost savings versus value. It this was a different workload, there could be benefits. But we are talking about AD that works just as well from Azure as on site and works BY FAR The best when kept in sync. If you keep the VM running, you get transparent failover 100% of the time. And you get to test it every day and know that things work.
-
@Breffni-Potter said:
As far as I can tell, Azure says you do not need to buy CALS, you pay for it with their hosting package. So the per hour fee you pay covers the server license along with hardware/bandwidth.
I've never seen that before. You need CALS not matter where the server is located.
-
@thecreativeone91 said:
@Breffni-Potter said:
As far as I can tell, Azure says you do not need to buy CALS, you pay for it with their hosting package. So the per hour fee you pay covers the server license along with hardware/bandwidth.
I've never seen that before. You need CALS not matter where the server is located.
I have a feeling that you do not need CALs "when accessing the Azure instances." That makes sense. They don't inform you of any additional licensing needs and by not doing so, they are implicitly licensing you what you have paid for. It's not like buying a server where someone has to agree to the usage rights. And this makes sense because of the way that capacity works.
But the moment you have onsight machines attached to Azure, you still need the CALs that you have always used, Azure doesn't cover that usage.
I'm not positive on this, but it makes business sense and is the only way that Azure is neither a loophole nor a financial windfall for large companies.
-
That was easy. And I was correct...
Does a customer need Windows Server CALs to connect to a Windows Server image that is running in Azure Virtual Machines?
No. Windows Server CALs are not required for accessing Windows Server running in the Azure environment because the access rights are included in the per-minute charge for the Virtual Machines. Use of Windows Server on-premises (whether in a VHD or otherwise) requires obtaining a separate license and is subject to the normal licensing requirements for use of software on-premises.
-
That's how we have always done it. We have CALs for our on premise systems and connecting to Azure doesn't give us extra use rights. But if we wanted to move to 100% Azure (which we are closing in on for production) then we could do away with CAL tracking as we are paying for capacity, not per user.
Think of Azure has having a third CAL type, the Capacity CAL.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Breffni-Potter said:
@thecreativeone91 Cisco...Dear god no.
Dell? Yes I've seen their warranty guys in action but still, for a service as simple as active directory and DNS, can we still not use hosted services as a redundant backup?
If it is JUST the services, why not run them in the cloud full time? That's what we do. We have AD and DNS out on Azure. So we can fail with application level failover and no one would notice.
how does licensing working for that?
Same as anything else. Server license is provided by the hosting agreement. You provide your CALs.
Oh that's right, Azure does have a licensing option for AD in their cloud.
-
@Dashrender said:
Oh that's right, Azure does have a licensing option for AD in their cloud.
Well sort of, but not how people mean it when they say that. Azure allows you to have Windows on IaaS the same as every other cloud vendor has had for a decade. Amazon, Rackspace, IBM, etc. have always (nearly) had Windows IaaS and Windows means AD. So AD is available running on Windows on an IaaS cloud instance, if that is what you mean, and that's nothing new. Nor is this CAL setup, this is all long established.
There is no SaaS AD from any cloud, any vendor. That's disallowed by Microsoft and you just can't do it and that is what every asked about and means when they say that someone has AD on the cloud.
-
@scottalanmiller said:
There is no SaaS AD from any cloud, any vendor. That's disallowed by Microsoft and you just can't do it and that is what every asked about and means when they say that someone has AD on the cloud.
Does that mean, if I spin up an Azure 2012R2 VM, I cannot install AD/DC services, then use that as my hosted domain controller? Slightly confused.
@thecreativeone91 said:
I've never seen that before. You need CALS not matter where the server is located.
I think I'd balk if MS said we needed to start doing CAL Tracking on Azure. Glad that's not the case.
-
@Breffni-Potter said:
@scottalanmiller said:
There is no SaaS AD from any cloud, any vendor. That's disallowed by Microsoft and you just can't do it and that is what every asked about and means when they say that someone has AD on the cloud.
Does that mean, if I spin up an Azure 2012R2 VM, I cannot install AD/DC services, then use that as my hosted domain controller? Slightly confused.
There is only one way that it could possibly work. You need CALs IF you have ANY Windows servers of your own. Azure is not a free pass to skip CALs. You have your own Windows servers already and you have your own CALs already. So you have no CAL worries.
-
@Breffni-Potter said:
I think I'd balk if MS said we needed to start doing CAL Tracking on Azure. Glad that's not the case.
Why? How would you be affected? You have to CAL track now. What new effort would be involved?
-
@scottalanmiller said:
There is only one way that it could possibly work.
Tell us more
@scottalanmiller said:
Why? How would you be affected? You have to CAL track now. What new effort would be involved?
Because if we're all going to move to hosted, then let's see if we can drop the back and forth of cal tracking and just focus on doing IT with these products.
@scottalanmiller said:
You need CALs IF you have ANY Windows servers of your own. Azure is not a free pass to skip CALs.
I know that, not implying that.
What I am trying to understand is how I can actually use Azure to do the AD, whether 100% Azure with no on site server OR a hybrid option. -
@Breffni-Potter said:
Why? How would you be affected? You have to CAL track now. What new effort would be involved?
Because if we're all going to move to hosted, then let's see if we can drop the back and forth of cal tracking and just focus on doing IT with these products.
One could argue that when you choose Windows, you choose to make IT all about license tracking
But it would simply be a lack of a benefit, not a new burden. Seems an odd place to be upset had that benefit not have been provided since you didn't balk when they had you do it on site for no reason either. You could have chosen Linux fifteen years ago and avoided all license headaches for all these years too. It would be really strange to eschew Windows now because they didn't drop the requirement after it's been acceptable for so long.
-
@Breffni-Potter said:
What I am trying to understand is how I can actually use Azure to do the AD, whether 100% Azure with no on site server OR a hybrid option.
There is nothing to know. Spin up a server, Hook up a VPN. Profit. That's all. Use it anyway you want. There is no licensing overhead to think about when working with Azure.
-
The only thing that you have to know is.... Azure is not a loophole. You don't get to STOP buying CALs. You just don't change anything. You operate like you always have. Everything is handled.
-
It would be really strange to eschew Windows now because they didn't drop the requirement after it's been acceptable for so long.
Dropping the need to worry about CAL tracking is only a plus. Windows 95 was acceptable for awhile but we've since moved onto better things (hopefully) Why would MS not drop CAL tracking if it makes life easier? What benefit does it have to anyone?
@scottalanmiller said:
The only thing that you have to know is.... Azure is not a loophole.
I'm not trying to cheat MS, Just trying to figure out their product.
-
@scottalanmiller said:
Seems an odd place to be upset had that benefit not have been provided since you didn't balk when they had you do it on site for no reason either.
Surely the reason was rampant software piracy, that's why we have the ever popular third party software audits. How can you pirate 365 or Azure? You either have the right license/billing amount or they switch you off.
-
@Breffni-Potter said:
Dropping the need to worry about CAL tracking is only a plus. Windows 95 was acceptable for awhile but we've since moved onto better things (hopefully) Why would MS not drop CAL tracking if it makes life easier? What benefit does it have to anyone?
They could have not created it in the first place if making life easier was the goal
-
@Breffni-Potter said:
@scottalanmiller said:
Seems an odd place to be upset had that benefit not have been provided since you didn't balk when they had you do it on site for no reason either.
Surely the reason was rampant software piracy, that's why we have the ever popular third party software audits. How can you pirate 365 or Azure? You either have the right license/billing amount or they switch you off.
But there could not have been piracy if they hadn't introduced it. If piracy was the only issue, not making CALs at all would have fixed CAL piracy
They did it to make extra money. Charge for the client. Charge for the server. Charge of the two together. They never had to do it, they've always had other options but opted for very complex ones.
-
@scottalanmiller I think you've just described another reason why I'd dislike CALS for Azure or other MS hosted services.
Imagine if they decided "Hey, you now need CALS for every 365 user, pay up"