I am trying to price out moving our company to azure or aws. I recently created a Azure VM at $45 a month.
2 Core +
4GB Ram +
8GB Temporary storage
I choose a HDD unmanaged disk when creating the VM. When I remote into the VM i see a 8GB D drive but I also see a 120GB C drive. What is the cost of the C drive?
Also how does this compare AWS, do they charge extra for this 120gb?
D drive is temporary and a free one (its not persistent). Its size depends on the VM SKU.
C drive is persistent and costs money. You can use Azure calculator to find out the cost (https://azure.microsoft.com/en-us/pricing/calculator/)
Related
I have created a SQL server 2016 virtual machine.
I have added 6 disks of 1 TB SSD each to my machine.
Is the pricing for each 1 TB disk the same as the premium storage disk (e.g. 148$ per month) or is there another pricing for the disks ?
Is the pricing for each 1 TB disk the same as the premium storage disk
(e.g. 148$ per month)
Yes, it is right. Only premium storage account supports SSD disk. Please refer to this link.
Billing for a premium storage disk or blob depends on the provisioned
size of the disk or blob. Azure maps the provisioned size (rounded up)
to the nearest premium storage disk option.
You select 4 1TB data disk, you need pay for 4 P30 cost(even you don't use them).
When creating the VM I'm asked about Storage configuration. When I select IOPS=0 (the minimum is otherwise 5000), Throughput=0 and Storage size=0, the info text is
0 data disks will be added to the virtual machine. This value was computed based on the value of IOPS, throughput, and storage size.
When the VM is created and I go to the Storage account, select Blobs and Container named vhds I see two disks, one 127GB and one 1TB disk.
Since the 1TB premium disks costs >100€/month I don't want that.
I tried removing the disk from a created machine but when I tried to add a new I got the error that "LUN :0 is already in use".
Preferably I would like to create machine correctly from the start. How can I do that?
This is correct. The current SQL Server IaaS experience on Azure Portal would creates one disk of 1TB even if specify 0 IOPS. We will add a fix to ensure the user cannot specify IOPS below 1 TB disk. If you need SQLVM without disks or any other configurations, you may use Azure PowerShell to create the VM.
I have a very unique question. In azure when you look at the pricing calculator and your deciding which size of VM to deploy for your cloud service the pricing calculator at the following URL
http://www.windowsazure.com/en-us/pricing/calculator/?scenario=cloud
shows storage along with the the size of the VM. For example the extra small instance says
"Extra small VM (1GHz CPU, 768MB RAM, 20GB Storage)" while the large instance shows "Large VM (4 x 1.6GHz CPU, 7GB RAM, 1,000GB Storage)".
My question is this. If I link a storage account to this cloud service do I get the listed storage in my storage account included with my payment for the cloud service. EG. I have a Large instance with a linked storage account and in the storage account I have 500GB of data stored. Do I pay 251.06 for the cloud service and an additional $36.91 for the 500 gb or is the storage free because it is under the 1000 gb limit listed as included storage for the cloud service?
Your question not unique, but rather common. The answer is - you pay for VM once and for Cloud Storage - second time. The point is that if you do Cloud Service (Web and Worker Roles) the storage that comes with the VM is NOT persistent storage. This means that the VM storage (the one that is from 20GB to 2TB depending ot VM size) can go away at any point of time. While the Cloud Storage (the cloud storage account - BLob / Tables / Queues) is absolutely durable, secure, persistent and optionally even geo-replicated.
I am confused about the Azure VM setup. I am trying to setup a SQL Server and the guidelines suggest that if your DBs are larger than 10GB, that you should setup a seperate Data Disk in Azure Storage. But all the documentation explicitly says not to use the D: Temporary Storage as it is volatile across reboots.
I completely understand this. The issue I have is that when I create a new VM, (I just created a SQL 2012 Web on 2008 R2 SP1 from the gallery), I get a single C: drive of about 128GB. When I then attach an empty data disk through the portal, it appears as D: and is called Temporary Storage.
My understanding is that this drive is not temporary storage (volatile) as I have created it through the portal as a data disk.
Is this a hangover from a past Azure configuration? I gather the VMs used to come with a 30GB OS drive but now come with a 128GB OS drive. Is this something to do with it?
I'm pretty confused!
The way it works, the D drive is the 70GB temp (volatile) drive (at least with Windows Server 2012):
Here, I just attached an empty disk and refreshed the windows Server disk manager. I then go to format it:
Once formatted, my new 20GB disk is assigned to F (and I still have a 70GB temp drive). This drive, backed by blob storage, is durable.
When you are using Azure VMs - the OS drive & the Data drives are backed by Azure Blob Storage (the VHDs are Page Blobs). The OS disk size limit during most of the CTP was 10GB, but was raised around the time the feature shipped to the larger 128GB. The deciding factor for Data Drive/No Data Drive/Lots of Data Drives (Max = 16) for SQL is more a function of your IOPS requirements than either the size of the DB corpus or the relative drive size.
For SQL workloads in a VM, I would strongly recommend reviewing:
http://go.microsoft.com/fwlink/?LinkId=306266
This is a performance paper based on the latest Azure bits, developed by the SQL team (updated June 2013).
Pat
In the interest of providing an answer to this question.
I think it was just an anomoly. #DavidMakogon helped me go through what was expected and it seems that my first VM simply didn't initialize the Temporary Drive on first boot, so this caused lots of confusion.
It's all working as expected now.
In my azure virtual machine i selected windows server 2008 r2 image from quick created. When I log into the machine, i see there are two drive. On which drive i should ftp my application because I am not sure which drive will persist if machine is moved.
Also how much data i can persist on each different type of VM, is there a limit depend on my vm size?
In Windows Azure Virtual Machine for Windows you can find drive C and D.
Drive C is the boot OS disk and the size is actually the size of your VHD you have either uploaded or configured from the Gallery. This disk is the persisted disk so anything you will store on drive C will be persisted. In the preview the Windows Server R2 VHD from Gallery id default 30 GB in size that's why you may see 30 GB size in drive C: however you can create upto 128 GB VHD and deploy by your own with medium and above Virtual Machine instance.
The storage space on drive D: is the temporary storage as indicated in the above table, where a Medium is expected to be 100 GB. This space is NOT peristed in Windows Azure storage and will be destroyed if the Virtual Machine needs to be migrated due to bad hardware.
About your question on how much data can be persisted on Windows Azure Virtual machine, the data size which can persist on Windows Azure Virtual Machine is documented here.
Extra Small - 20 GB
Small - 20 GB
Medium - 100 GB
Large - 200 GB
Extra Large - 400 GB
Each Azure virtual machine has, by default, two drives. The default c: drive is a vhd in blob storage connaected as storage to your virtual machine and is the persistant drive. See the technical diagram and description of creating virtual machines here: http://www.windowsazure.com/en-us/manage/linux/other-resources/command-line-tools/
Any drives you connect to the virtual machine will be, ultimately, vhd's in blob storage.
Yes, the limit does depend on your VM size.
Each data disk that you attach to an Azure Virtual Machine has a maximum capacity of 1 TB (current max size for a page blob which backs this data disk). So with an extra large VM you can have 16 TB of persistant geo-replicated storage (if you enable this in your storage account).
VM Size Data Disk Limit
Extra Small 1
Small 2
Medium 4
Large 8
Extra Large 16
http://www.windowsazure.com/en-us/manage/windows/how-to-guides/attach-a-disk/