The capacity is already set to one terabyte, so we don’t need to change that, but let’s say we also have five terabytes of backup and ten terabytes of archive storage. I’ll leave these options as is, but let’s say we need 1,000 gigs of backup storage. The one that’s the most compatible with SQL Server is “SQL Database Managed Instance”, so we’ll set it to that. And let’s put 2 processors per server, 4 cores per processor, and 8 gigs of RAM per server.ĭown here, we need to tell it which Azure service we want to use because there are a few options. We need to change the servers to 2, though. All of these options match our example, so we’ll leave them with the defaults. I said we have two SQL Servers, so we’ll click “Add database”. If we wanted to define more workloads, we could click here and add another one, but we only have one workload in this example, so we’ll move to the next section. You only need to enable this option if you’re running Windows Server 2008, so we’ll leave it disabled. If it can’t find an exact match, then it will look for a VM size that’s close, but it will make sure it has enough cores if we tell it to optimize by CPU, or it will make sure it has enough RAM if we tell it to optimize by memory. If it finds an exact match, then it ignores the “Optimize by” setting. When the calculator comes up with recommendations for Azure Virtual Machines, it tries to find a VM size that’s an exact match for the number of cores and gigs of RAM we specified. This “Optimize by” option will take a bit of explaining. And let’s say we have 16 gigs of RAM per VM. Let’s say we currently have 8 cores per VM. This is the number of core or virtual CPUs per virtual machine. And it’s already set to Hyper-V for the virtualization. This is where we say that we have 20 virtual machines. And let’s say we have a Windows Datacenter license. Since I said that the 20 webservers are running on Hyper-V, we’ll need to change this to virtual machines. Since we’re currently running on Windows servers in this example, we’ll leave the workload type as “Windows/Linux Server”. The information we need to fill in is what we’re currently using on-premises. Okay, first we need to define our workloads, starting with servers. You don’t need to have an Azure subscription to access it, of course, because the whole idea is to use it before you migrate your workloads to Azure. Suppose we want to move these workloads to Azure: 20 Windows-based web servers running on Hyper-V, two physical SQL Servers, and one terabyte of storage. You can choose any time period between one and five years to compare the costs. For example, the cost of electricity used by the calculator may be different from what you typically pay, so you can adjust that number. Second, adjust the assumptions used by the TCO Calculator. These fall into four categories: servers, databases, storage, and networking. It uses industry averages for on-premises costs, and of course, the equivalent costs on Azure. This includes obvious costs like hardware and software but also many other costs, such as electricity, real estate, and labor.įortunately, Microsoft provides a useful tool called the Total Cost of Ownership, or TCO, Calculator. This can be a daunting task because not only do you have to figure out how much everything will cost on Azure, but you also have to make sure you include all of your current costs for your on-premises infrastructure. If your organization is thinking about moving some or all of its IT workloads from an on-premises data center to Azure, one of the first things you’ll want to do is compare the cost of the two environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |