I have created a VM in hyperv using dynamically expanding VHD option.Now I have exported that VHD to azure cloud and created a VM in azure.My VM is not booting properly. Is it recommended to use dynamically expanding VHD to create VM in azure?
OS and Data disks (ephemeral storage is local to the hardware) are thin provisioned in Azure. That is they are dynamically expanding. This is a decision made by Azure (so they don't have to store hundreds of thousands of mostly empty 120gb C: drives, which also makes it cheaper for you. ) and there is no option to change that.
Disks that you upload need to be a fixed size. (so you will pay for the full size)
According to Azure Documentation - Upload a Windows VM image to Microsoft Azure for Resource Manager deployments
Microsoft Azure can only accept images for Generation 1 virtual machines saved in the VHD file format. The VHD size must be fixed and a whole number of MB. The maximum size allowed for the VHD is 1023GB.
If you are having problems with an uploaded disk, it is likely that the problem is that you have created a dynamically expanding one and it simply isn't booting.
Usually, you want to create the VM with a fixed size disk as the dynamically expanding disks have a performance cost.
More information here:
https://technet.microsoft.com/en-us/magazine/ff458359.aspx
Related
I have created a VM (Standard DS11 v2) on Azure about 2 - 3 weeks ago. It attached a premium disk which has extra price. (I did not know that when I created the VM.)
Now I want to change this disk to a standard disk. As I see, it is not possible to downgrade a premium disk to standard.
What I am trying to do is:
Attach a standard disk to my VM.
Copy premium disk to standard disk.
Make standard disk OS disk.
Detach premium disk.
Delete premium disk.,
How can I do that?
Also I am open to different solutions to my problem.
My OS is Centos 7.2.
You could not resize Ds series VM to D series VM.
Based on my knowledge, you could recreate your VM by using your VHD.
Please refer the following steps.
Stop and delete your VM but don't delete the VM's VHD.
Create a new standard storage account and blob container in the same resource group.
Copy VHD to the new storage account, you could use Azcopy.
AzCopy /Source:https://shuidisks446.blob.core.windows.net/vhds /Dest:https://shuidiag102.blob.core.windows.net/vhds /SourceKey:sGqtdFHQWQWYyf2tRWGF5jkeAEubTp13AVaeTM25QogxXE+K0Ezq1ulcs18qGVPhCEp6ULdLLbKVa7fMbUvYZg== /DestKey:iCjeS+eegjkSJXHjH2UqCkqXnUPiCGvxaOG0Ad2LoPgUnvBoWl9wQJtC1jc//lOj4CF7khpLQe791P4QeyTY6Q== /Pattern:shui20161222141315.vhd
More information about Azcopy please refer to this article.
Use the VHD to create a D series VM. It is easy for you to recreate with existing VHD by using this template
Delete your Premium Storage Account.
I am using two Microsoft Azure Virtual Machines (marked as classic), both running on Linux. One is used for test purposes and internal demos, the other is production and running few of clients' instances.
What I would like to do is change the size of Virtual Machine. I understand this is quite common process and can easily be done from the Azure Management Portal and that this is not affecting data. However, when I have changed the size of our testing machine, exactly this has happened and we have lost all data.
Azure Support answer received was:
"We recommend you delete the VM by keeping the attached disks and create a new VM with the required size." Not sure why this would be better?
Any data stored on the ephemeral (internal-to-chassis) scratch disk is at risk, as it's a non-durable disk (and will in all likelihood be destroyed/recreated upon resizing a VM).
The only way to have durable data is to use Azure Storage (blobs, vhd as attached disk, Azure File storage) or external database. Azure Storage is durable (minimum 3 copies), and is not stored with your VM.
One more thing: The VM's OS Disk is a VHD in Azure Storage (so the OS disk is durable, just like attached vhd's).
You have more than one way to do that and keep in mind what David said, data on OS disks, attached disks and blobs is the only durable one.
To prevent losing data and since you're using Classic VMs, you can do the following:
1- Go to your VM on portal and capture an image out of it.
2- Go to your new image and create a new VM out of it, while specifying the new specs that you need.
3- When done, connect to your new VM while keeping the old one without termination.
4- Check if all your data is there, if yes, then you can remove the old one. (In case you need the old IP, you can still assign it to the new one).
Cheers.
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 virtual machine running Windows on Microsoft Windows Azure. I am noticing that one of the hard drives shows as completely full. Do these drives automatically expand as data is added, or do I need to increase storage, and if so--how?
Thanks for any tips.
In Azure, both the OS Disk and any attached Data Disks are fixed format VHDs. They are not resized automatically and, in fact, there is no supported process to modify the size. Since these disks are allocated using sparse storage - i.e., you are only billed for space actually used - the general recommendation is to use 1TB disks. If the disk is empty you will not be billed.
Windows Server 2012 provides TRIM support which clears the space occupied in Azure Storage by deleted files. Without this support there could still be a charge for files which have been deleted from the filesystem but which still occupy pages in the page blob backing the VHD in Azure Storage.
Martin Balliauw has written up instructions for modifying the size of a VHD in Azure. He has also created a utility that helps with this task. This comes with a do it at your own risk warning.
I want to create a linux VM that can accomodate up to 10 terabytes of data. Not sure how to accomplish that on Microsoft Azure or if it is even possible. Any insight would be appreciated.
You create the storage separately from the VM - they have a data servuce known as BLOB service in Azure
Here is a link http://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-how-to-use-blobs/
supporting many terrabytes is not a problem
You create one Linux VM from image and then attach (via Azure portal, like here) 10 disks of 1TB each. Today 1TB is the max size of a disk in Azure. As for the VM, you will need to have an Extra Large VM in order to accept this number of disks (up to 16 disks for an XL).