Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I currently attached a data disk of 1 GB to Windows Extra Small VM running on Azure.
How do I increase the size of data disk without losing data?
Is it possible to attach many more disks to Extra Small VM especially from other storage accounts?
It is possible to attach more disks into an Extra Small VM.
It isn't possible to increase the size of data disk in Disk Management. But with some extra steps you can accomplish that by downloading the VHD into a larger disk attached to a different VM, mount it and extend it, then put it back where it was and attach it again to the original VM.
Please check Drew's description here
How do I increase the size of data disk without losing data?
I don't think you can increase the size of the data disk.
Is it possible to attach many more disks to Extra Small VM especially
from other storage accounts?
You can attach another data disk. You can attach up to 16 data disks to a VM. Since the data disk is essentially a page blob, you are only charged for the space you occupy and not the actual size of the disk thus it is advisable to attach a larger size data disk so that you don't run out of disk space. Though I have not tried attaching data disks from different storage accounts but I can't see a reason why it should not be possible (they should be in same data center though). However you may want to keep all your OS and Data Disks in the same storage account for improved latency purposes. HTH.
Related
Good Morning, Fellow Stack Overflow-ers,
I have a Windows 2019 DC Virtual Machine with a 127GiB OS Disk with MS Azure. The WM image is Standard B2s (2 vcpus, 4 GiB memory)
I want to swap this with a smaller 8GiB OS disk - having successfully created this in my portal and labelled useastOS - Azure is failing to allow me to swap from the previous 127GiB disk to the smaller 8GiB Disk. On the "Swap OS Disk" menu illustrated, you will see there is no option to use the useastOS disk.
Puzzling.
This is a managed disk and so there is no reason whatsoever as to why Azure is not giving me the option.
So my question is there any valid reason as to why Azure is not allowing me to swap to the smaller useastOS or is this bug within Azure that I need to make Azure aware of?
When you are creating a Managed Disk like this, there is no SO installed, it is an empty disk, that's why Azure assumes it is a data disk, not a SO disk.
Now, when you upload your VHD disk to blob storage, you can tell Azure that this disk is OS and not a data disk like this.
Looking for upload VHD to Azure blob, here it is an example https://learn.microsoft.com/en-us/azure/virtual-machines/windows/prepare-for-upload-vhd-image.
Your question is how to swap SO disk to a new one smaller, this is what I understood, in case you just want to add a second disk as a data disk, you can go to VM overview, from blade disk, you can add it easily.
Anyway, I hope that I could help in any :)
Just in case, confirm that you selected an operation system when you created this disk useastOS. For example, in my case it is Windows, but disk can be either Windows or Linux, when you don't select anything, Azure assumes it is a data disk, not an operation system.
I need to know the difference between the SSD disk and the data disk. According to this capture, this virtual machine has a hard disk ssd 16gb, and 4 disks data. But these 4 disks, how much do they have? Are they ssd? what are they for?
enter image description here
data disks can be ssd or not, depending on how you set them up. they are used to store data :)
amount of data disks you can attach depends on the vm sku. you dont always have to attach 4 data disks (or whatever vm supports, you can have 0 - VM SKU maximum data disks).
The 16gb ssd is local ssd (local to the host machine hosting your vm) attached to the VM (not OS disk). its a temporary drive - meaning it can go away when you reboot vm, so content will be lost and you will get a new temporary drive. it can be used to store throw away logs, for example, or temporary files. IO operations on this disk do not count towards IO limit and this drive is completely free (you pay for the VM SKU and it is part of that cost).
you can learn about data disk prices here: https://azure.microsoft.com/en-us/pricing/details/managed-disks/. Storage prices do not take into account os or data disks. they just bill you for storage.
reference:
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/attach-managed-disk-portal
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/attach-disk-ps
It means in addition to the OS disk, you can connect 4 data disks to the VM.
It does not mean there are 4 disks, just that you can add 4 if you want.
You should discuss the VM requirements with your client. Maybe he needs an additional data disk, maybe not.
The capture you posted, specifies that this VM can take up to 4 data disks. The price does not include them. Also, you should check the Azure price calculator to generate more accurate offers.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am new to Azure. I have created a VM. and stored some very important files on temp storage, but after few days the temp disk is formatted. is there any option I can get my data back ??
Eshant
Just wanted to provide you with clear guidance regarding the disks and why you lost data. There are 3 Disks with in Azure VM, the are as follows
C Drive 127 GB Dedicated for OS will persist after reboot. This disk is dedicated for OS and shouldn't be used for any other purpose.
D Drive is Temporary Drive is only intended for storing temporary data. As you notice it only has page file on it and is not recommended for storing data because it is wiped clean on Stop and start, resize of VM , un/planned maintenance, and service healing. One key benefit of this disk is performance. I/O performance for temporary disks is higher than the IO permanence to OS disks, Data Disks. The size of the disk varies with VM Size. In your case the data is lost and cannot be recovered.
Data Disk. You need to add Data disks for any type of custom storage that needs to be persisted. Another point being ,the difference between OS and data disks is that, while both reside in blob storage, the host caching settings are different by default - OS disk is Read/Write host caching by default, data disks are None host caching by default.
One key point is , the C:\ and D:\ cost is included in the VM Price , Data disk will be charged on actual usage. Say if you allocate 100 GB and use only 10 GB. Then you be charged only for the 10 GB.
Regards
Krishna
No, there's no way to recover your data.
From this Microsoft article: Understanding the temporary drive on Windows Azure Virtual Machines
http://blogs.msdn.com/b/wats/archive/2013/12/07/understanding-the-temporary-drive-on-windows-azure-virtual-machines.aspx
Is there a way to recover data from the temporary drive?
There is no way to recover any data from the temporary drive.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
The community reviewed whether to reopen this question 1 year ago and left it closed:
Original close reason(s) were not resolved
Improve this question
So i'm looking for a cost affective way to host a website in a linux vm. The pricing only states the VM's cpu and RAM. What about the space used up by the OS and apps in the VM as well as the ongoing disk usage? is this an added cost? Whats the size of the disk?
I get tired of going round in circles and getting confused every time (twice now) I set up a new VM. So here's what I've found:
Let's say I choose the DS1_V2 virtual machine, which supports premium (SSD) storage. (This just means the physical azure node with your VM on it allows use of SSD as an drive. I assume all new configurations support SSD and it's just legacy hardware that doesn't but I'm not 100% sure on this.)
The monthly price is currently about $100 for this VM. You only get included what you see here:
So the 7GB local SSD disk size here is included in the $98.95, but you get no other storage. This 7GB vanishes when you reboot anyway so you can't use it for real storage.
When you create a VM you have a choice between HDD and SSD. The 'new VM wizard' encourages you to select SSD but doesn't tell you what pricing that will incur. This I think is very misleading and a source of confusion and probably why you are now reading this.
Anyway - let's say you picked SSD (which I did). You'll get a 127GB drive as your C:\ and the temporary storage in addition as your D:\
In your account portal you will see two items created
To confirm how this drive is configured you must click on it and you'll see something like this :
When you choose an SSD for your operating system it will default to 127GB but you will always pay for the full drive. Note that you can switch between HDD and SSD, but you need to reboot the VM.
The current pricing for 128GB (which is what they call a P10 disk) is $19.97 a month. So the total price for your VM will be fixed at $98.95 + $19.97 a month as long as you use SSD. To put it another way you're paying for a P10 disk that just happens to be used as your VM's operating system.
SSD Drive Pricing
As a comparison for HDD you only pay for what you use. If you used up the whole 127GB you'd be paying around $2.94 extra instead of $19.97. So SSD is really a minor expense but not negligible and certainly NOT included..
HDD Drive Pricing
And then in your billing you will see it listed as P10
I have two VMs set up with SSD so they are charging me $39.47/2 = $19.74 for each one.
EDIT June 27, 2014 - updated pricing to be current (this answer was two years old).
Your Virtual Machines are each stored in blob storage. So, if your machine image takes up, say, 20GB, you are now paying for 20GB of storage (actually, you only pay for storage used within that 20GB disk, as Azure's vhd's are stored in a sparse format).
At 12.5 around 2.4 cents per GB (locally-redundant storage, which you'd use with vhd's), and you actually used all 20GB, you're talking less than 50 cents monthly. You'll also pay a penny half-penny per 100,000 storage transactions. even though your VM disk volume looks like a formatted drive, its underlying storage is Blob Storage; gets and puts result in metered transactions.
More details on storage costs are here.
This has changed with Premium Storage, which gives you SSD disks. You pay for the full SSD disk regardless of how much data is on said disk. SSD disks come in 3 sizes, 128GB, 256GB, 512GB.
I`ve created a tool http://azureprice.net to compare azure VMs and bunch other stuff that can help choose the cheapest VM, region, and currency. Probably somebody finds it helpful.
http://msdn.microsoft.com/en-us/library/windowsazure/ee814754.aspx
Lists how much storage you get for the instance size selected. I beleive your OS does take up that number. So an extra small instance gives you 20GB of space. and if you OS is 5GB you will have 15GB for app useage.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
How stable is s3fs to mount an Amazon S3 bucket as a local directory in linux? Is it recommended/stable for high demand production environments?
Are there any better/similar solutions?
Update: Would it be better to use EBS and to mount it via NFS to all other AMIs?
There's a good article on s3fs here, which after reading I resorted to an EBS Share.
It highlights a few important considerations when using s3fs, namely related to the inherent limitations of S3:
no file can be over 5GB
you can't partially update a file so changing a single byte will re-upload the entire file.
operation on many small files are very efficient (each is a separate S3 object after all) but large files are very inefficient
Though S3 supports partial/chunked downloads, s3fs doesn't take advantage of this so if you want to read just one byte of a 1GB file, you'll have to download the entire GB.
It therefore depends on what you are storing whether s3fs is a feasible option. If you're storing say, photos, where you want to write an entire file or read an entire file never incrementally change a file, then its fine, although one may ask, if you're doing this, then why not just use S3's API Directly?
If you're talking about appliation data, (say database files, logging files) where you want to make small incremental change then its a definite no - S3 Just doesn't work that way you can't incrementally change a file.
The article mentioned above does talk about a similar application - s3backer - which gets around the performance issues by implementing a virtual filesystem over S3. This gets around the performance issues but itself has a few issues of its own:
High risk for data corruption, due to the delayed writes
too small block sizes (e.g., the 4K default) can add significant
extra costs (e.g., $130 for 50GB with 4K blocks worth of storage)
too large block sizes can add significant data transfer and storage
fees.
memory usage can be prohibitive: by default it caches 1000 blocks.
With the default 4K block size that's not an issue but most users
will probably want to increase block size.
I resorted to EBS Mounted Drived shared from an EC2 instance. But you should know that although the most performant option it has one big problem
An EBS Mounted NFS Share has its own problems - a single point of failure; if the machine that's sharing the EBS Volume goes down then you lose access on all machines which access the share.
This is a risk I was able to live with and was the option I chose in the end.
This is an old question so I'll share my experience over the past year with S3FS.
Initially, it had a number of bugs and memory leaks (I had a cron-job to restart it every 2 hours) but with the latest release 1.73 it's been very stable.
The best thing about S3FS is you have one less things to worry about and get some performance benefits for free.
Most of your S3 requests are going to be PUT (~5%) and GET (~95%). If you don't need any post-processing (thumbnail generation for example). If you don't need any post-processing, you shouldn't be hitting your web server in the first place and uploading directly to S3 (using CORS).
Assuming you are hitting the server probably means you need to do some post-processing on images. With an S3 API you'll be uploading to the server, then uploading to S3. If the user wants to crop, you'll need to download again from S3, then re-upload to server, crop and then upload to S3. With S3FS and local caching turned on this orchestration is taken care of for you and saves downloading files from S3.
On caching, if you are caching to an ephemeral drive on EC2, you get a the performance benefits that come with out and can purge your cache without having to worry about anything. Unless you run out of disk space, you should have no reason to purge your cache. This makes traversing operations like searching and filtering much easier.
The one thing I do wish it has was full sync with S3 (RSync style). That would make it an enterprise version of DropBox or Google Drive for S3 but without having to contend with the quotas and fees that come with it.