I am trying to mount an Azure storage account to a VM by following:
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-quick-create-use-linux
Seems it works, but I need to re-mount after VM reboot.
Can I update /etc/fstab so it will auto-mount after VM reboot?
Currently I specify the Azure file storage account size when creating it (100GB in the example). Can I mount to a Azure file storage account without specifying size, so it can auto-scale and pay as it goes?
Thanks.
If you want to mount a NFS file share permanently even after the vm reboot then you need to update the fstab as explained in this documentation
Can I mount to a Azure file storage account without specifying size,
so it can auto-scale and pay as it goes?
No you cannot.NFS file shares are supported for premium storage accounts only. 100GB is the minimum storage/quota allocated when you create a NFS file share and you can expand up to 102400GB by using change size and performance option as shown in below image
Related
Is there a way to mount an Azure blob account as a drive in a linux machine, and have the files show up as file blobs in the Azure portal? I know I can mount an Azure blob as a disk, but when I'm done, I just have a disk. I'm looking to backup a few critical files from an Azure VM, and don't really want to rig up SDK calls. I'd rather a cron rsync a directory -- added benefit: it prunes. I'm familiar with rclone and AzCopy, but both require I bake azure secrets into the command line. Is there a blob mount way to do it instead of a separate install?
You can use blobfuse to mount a Blob storage container on Linux and access data. Blobfuse is a virtual file system driver for Azure Blob Storage, which allows you to access your existing block blob data in your Storage account through the Linux file system. Azure Blob Storage is an object storage service and therefore does not have a hierarchical namespace. Blobfuse provides this namespace using the virtual directory scheme with the use of forward-slash '/' as a delimiter.
there is Mount for Files
https://learn.microsoft.com/en-ca/azure/storage/files/storage-files-introduction
Do not try Mount with Windows SMB DISASTER!!!
Mount Azure File storage on Linux VMs using SMB
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/mount-azure-file-storage-on-linux-using-smb
ONE MORE TIME SMB= DISASTER!!!!
there are 3rd party tools like for BLOBs
https://www.cloudberrylab.com/
https://www.cloudberrylab.com/backup/linux.aspx
personally I look to develop by myself app and backup on demand not as permanent disk attached Hard to secure...
READ HERE
https://www.google.ca/search?q=hack+smb+share
goofys added support for azure blob: https://github.com/kahing/goofys/blob/master/README-azure.md#azure-blob-storage
read this mount -t nfs vs cifs already :( ?
Our requirement is that we have an application hosted in AWS using nfs-utils to mount a EFS for use ? My question is how can this be done in Azure. I know they have Azure files which works in quite similar way to EFS but as per azure documentation it is done only through cifs-util. Point is that though it will mount a Azure file share in Azure will it work without any issue or do we need to do something in our commands to make it happen?
I am not good in linux, so please pardon me if I am sounding total stupid.
Our requirement is that we have an application hosted in AWS using
nfs-utils to mount a EFS for use ? My question is how can this be done
in Azure.
Amazon Elastic File System (Amazon EFS) provides simple, scalable file storage for use with Amazon EC2 instances in the AWS Cloud.
If you want do the same thing in Azure, I think you are talking about Azure storage blob(new disk).
In Azure, we can via Azure portal to add a new disk to Azure VM as a data disk, works like add a physical data disk to a host. Then we can use fdisk to create the file system on the new partition.
We can follow this article to attach a new disk to Azure VM via Azure portal.
After that completed, we can follow this article to initialize a new data disk in Linux.
I know they have Azure files which works in quite similar way to EFS
but as per azure documentation it is done only through cifs-util.
You are right, Azure files share works like EFS, but Azure files share use Server Message Block (SMB) protocol(also known as Common Internet File System, or CIFS).
The maximum size of an Azure file share is 5 Tib, there is a quota of 20,000 open handles on a single file, and the max IOPS per share is 1000 IOPS.
We can create data disk from Azure storage blob, the maxium size of data disk is 4 Tib(we can create multiple data disks to that VM), and OS disk is 2 Tib.
AWS EFS suppoer Network file system versions 4.0 and 4.1(NFSv4) protocal.
Here a article about performance about Azure file share and Azure storage blob.
How can I change the disk type in an Azure storage account disk from Premium to Standard (SSD to HDD)?
For example, in my windows server VM the disk is configured to be a Premium. I no longer need it to be an SSD for the type of usage so I would like to change it to Standard. But it is greyed out. The VM is not currently running.
The disk type is configured at the time of creating the Azure Storage Account. The disk type is used to determine the physical hardware that hosts your Azure Storage Account within the Azure data center.
Currently, you are NOT able to change the disk type of a storage account after creation, and it's tied to that particular disk type. Unfortunately, if you need to change disk types, then you will need to copy your VM .vhd disk images to a new storage account that uses HDD disk type, then create the Azure VM to use the .vhd disk image from the new storage account.
I created a Azure Virtual Machine and it in turn created a temporary storage drive for me (D:). Now, If I have C:, D:, E:,F: drive in my VM how can I differentiate which is Azure temporary Storage which is not.
I have tried to Use DeviceType=3 but it lists all the Logical Drives.
I'm assuming you're talking about Virtual Machines (you didn't specify). For VMs:
Your OS disk is backed by durable blob storage. All the time. For Windows, this is approx. 127GB. For Linux, this is approx. 32GB.
Your temp drive is always in-chassis, and at risk. The temp disk size is advertised in the VM sizing specs.
Beyond that: You'd be taking the specific action of mounting additional disks, which are all durable, blob-backed. So you'll know exactly which drives there are.
After some research, it looks there isn't any programmatic way to identify the Azure temporary drive. May be the hack is to look for "DATALOSS_WARNING_README.txt" file in all the drives.
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.