Storage
-
Enable immediate sync after changes on the Azure file share for Azure File Sync
When I make a change on my server endpoint (Windows File Server), Azure File Sync initiates a sync session very quickly after file save, however for changes on the cloud endpoint (Azure file share), I have to wait at least 24 hours to have changes get synced down to my server endpoints.
Please invest in features to initiate a sync session immediately after changes are made cloud-side, or at least increase the interval of sync from the Azure file share.
773 votesThanks for your feedback! As you mentioned, we initiate a change detection job once every 24 hours to enumerate the Azure file share and scan for changes. This is required for the Azure file share because Azure Files currently lacks a change notification mechanism like Windows Server has (we watching the USN journal on Windows Server to automatically initiate sync sessions on the server after changes are made).
Long term, we would like to build a change notification mechanism directly into Azure Files. Shorter term, we could use your feedback to understand how painful the once every 24 hours change detection is for you. Please vote and/or leave comments on this item to let us know we should invest in work to make the change detection job run more frequently/faster.
Thanks,
Will Gries
Program Manager, Azure Files -
Schedule snapshots of Azure file shares
I want to schedule snapshot of Azure Files.
Every morning, Every Monday, etc.
For trouble each users, they can restore files at morning. or Monday.
IT pro can say, Hey you can back to morning who trouble any.240 votesThank you for your feedback! We working to provide this functionality through the Azure Backup offering. They are currently testing this functionality in a private preview, and are going to be entering a public preview soon. I will update this feedback item as soon as this is released.
Thanks,
Will Gries
Program Manager, Azure Files -
Ability to manually initiate failover on Geo-Redundant storage accounts (GRS & RA-GRS)
GRS & RA-GRS storage accounts currently geo-replicate all contents from a primary zone's storage account (storageA) to a secondary zone's storage account (storageB) automatically and this is wonderful.
Right now, it is Microsoft that control when the failover occurs from storageA to storageB. It is also very well documented that this switch will happen only as a last resort move because of the complexity of switching all accounts, possible data loss, etc...
For advanced DR scenarios it would be very handy for us to have a way to manually trigger the failover switch between storageA and storageB.
After the manual…
218 votesThank you for your feedback. We are working on customer controlled failover for both disaster and DR drill scenarios. Please contact xstoredr@microsoft.com for more details about enrolling in a private preview, and for any further questions.
-
Enable multiple custom domains for storage accounts
I would like to register 2 or more custom domains to point to 1 storage account.
For example, foo.com, bar.com both point to blob.etc.windows.net
208 votesThank you for your feedback. Enabling multiple custom domains for a single storage account is planned for the coming year. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Azure Files and Azure File Sync must support all unicode characters
Azure Files and Azure File Sync do not support all unicode characters/characters supported by NTFS. This is particularly challenging when working with languages with non-Latin charactersets (see this post on issues supporting Japanese charactersets: https://social.msdn.microsoft.com/Forums/ja-JP/1ed730a9-9a4d-40dd-b84e-6f184e35e633/).
This is also a significant adoption blocker when trying to adopt Azure File Sync, as file names on NTFS that are valid are rejected by Azure Files.
105 votesThank you for the feedback! This is an issue we are aware of and are actively working to close this gap this year. Please feel free to continue to vote for this item to help us prioritize this effort.
Thanks,
Will Gries
Program Manager, Azure Files -
Add support for Server Core installations for Azure File Sync
Currently only the full UI versions of 2012 R2 and 2016 are supported. Add support for core installations.
96 votesThanks for your feedback! We are planning to add support for Server Core installations. We’re not taking any dependencies in the Azure File Sync agent on Full-only features, so supporting Core should be relatively straight-forward, however we do have two small dependencies to unwind. First, we have a dependency on the AzureRM PowerShell module, which right now requires Internet Explorer to be installed (which obviously is not available on Core). Second, we are working to make sure our installer is completely configurable from in an unattended mode.
Please continue to vote for this item to help us prioritize (and to help the AzureRM team have the evidence to support Windows Server Core).
Thanks,
Will Gries
Program Manager, Azure Files -
Scale to Premium Storage from standard Storage
Please allow us to switch from Standard Storage to Premium Storage and the other way around. Or at least provide us with the option to scale up from Standard Storage to Premium Storage (one way).
The current process involves stopping the affected VM, copying the disk using AzCopy and recreating the VM in the new storage account.
I'm pretty sure Micorosft's team can take care of this process behind the scenes and just provide us with a user interface option and/or an API method.Currently we have multiple VMs (about 20+) running on standard storage that need to be upgraded…
53 votesAzure Storage is actively working on features that could improve the migration story from standard to premium disks.
-
Auto defragment append blobs
Append blobs are great, however, when a such a blob is generated through a long series of small increments, the read performance of the resulting blob is very poor: from 10x to 20x slower than reading a regular page blob.
The performance problem goes away if the app rewrite the append-blob in large 4MB chunks. However, this process is complicated to setup, and collides with any 'always-on' property of the app.
As append blobs are append-only, it would be much better if Azure was taking care of defragmenting the append blobs on its own; possible through a dedicated API operation…
52 votesThank you for your feedback. This work is planned for the coming year. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Make it possible to send Storage Analytics ($logs) to Log analytics
Currently Storage accounts can generate detailed logs which are stored under $logs in the storage account. But it is not possible to link this to Log Analytics. This functionality would enable monitoring data access, which is sometimes a regulatory requirement.
44 votesThank you for your feedback. Providing this functionality is planned for the coming year. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Changeable "last-modified" file property on Azure File Service
At the moment, our application stores its documents in a normal folder on a network share. The “Last Modification Time” of the files are important for internal version-handling, and our application heavily uses this file-property.
Now we decided to move our documents into the cloud and we started using Azure File Service Preview. When we upload the documents via REST API, the “Last-Modified” property of the uploaded files get the current-time – that’s reasonable.
But unfortunately afterwards the “Set File Properties” REST API call (https://msdn.microsoft.com/en-us/library/azure/dn166975.aspx) does not support the change of the “Last-Modified” property. (I tried both with…
37 votesThanks for this feedback. Long term, we would like the File REST API for Azure Files to be a superset of the functionality available in SMB. In the short term, we are looking to close some of the gaps in the API that are most painful, like the file attributes that you can set via SMB but not File REST.
We would appreciate further feedback on this item, in particular feedback on the things that you can do today over SMB but not REST to help us prioritize the order in which we close the gap!
Thanks,
Will Gries
Program Manager, Azure Files -
[Feature Request] Please enable customer to use alert rule and capacity graph for Premium Storage Accounts.
According to the document below, Premium Storage Accounts have the following limits.
- Azure subscription and service limits, quotas, and constraints
<https://azure.microsoft.com/en-us/documentation/articles/azure-subscription-service-limits/>
------
Total disk capacity per account 35 TB
Total snapshot capacity per account 10 TB
Max bandwidth per account (ingress + egress1) <=50 Gbps
------We need to manage these capacities so that we can execute operations for Premium Storage Account without error.
Please enable customer to use alert rule and capacity graph for Premium Storage Accounts.- Japanese
以下のドキュメントによるとプレミアムストレージアカウントには上限があります。- Azure サブスクリプションとサービスの制限、クォータ、制約
< https://azure.microsoft.com/ja-jp/documentation/articles/azure-subscription-service-limits/ >
------
アカウントごとのディスク容量合計 35 TB
アカウントごとのスナップショット容量合計 10 TB
アカウントごとの最大帯域幅 (受信 +…31 votesAzure Storage is currently working on features that would address this problem.
-
Allow smaller premium drive sizes for VM
Currently the smallest premium disk size when creating a VM is 128 GB. We have many VM's that are used solely for computation intensive workload and large amounts of data are not stored to the operating system drive. A 64 GB option would be sufficient for the space we are using and help to reduce some of the premium storage costs.
23 votesAzure Storage is actively working on features that would address this concern.
-
Increase the number of attached Disks per Core
Please allow attaching more disks per core, or increase the max size of disk (1TB by default) without forcing upgrading the VM instance.
For my project I use A1 Standard VM instance and CPU/memory is sufficient for my project, but it needs more storage (up to 10TB).
I can't attach more disks without spending more on CPU/memory that my project doesn't require.
I think, we should be charged for capacities/storage we really use and not for what we're forced to use!
Please support it!10 votesAzure Storage is actively working on features that could address this request.
-
Implement viewer for json / csv blob files
At the moment the only way to view a files in storage blobs is to download it and open it within an editor. This is fine for larger files, but for the smaller ones it would be a bit easier to be able to get a quick (pre)view of the file in the browser by just clicking it. Should not be that hard to implement an additional pane with a view of the raw file contents.
9 votesThank you for you feedback. This work is planned for the coming year. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Display OS Disks and VM Images in Delete storage account blade
There's many 'cannot delete storage resource' questions caused by OS disks or VM image references such as below;
- https://feedback.azure.com/forums/217298-storage/suggestions/11525553-cannot-delete-storage-account
- https://feedback.azure.com/forums/217298-storage/suggestions/10976463-failed-to-delete-storage-account-10-51-am-failed-t
- http://stackoverflow.com/q/34362904/361100It would be good to provide VM disks and OS images information in "Delete storage account" blade summary page.
8 votesAzure Storage is actively working on features that could address this problem.
- Don't see your idea?