my question is about Microsoft Azure blob storage.
Can I manage blob snapshots from user console (azure portal)? Take snapshot,delete,recover etc.
Thanks
No, currently the portal does not offer this functionality. You may want to check out Azure Explorers available in the market. Most of them have support for managing blob snapshots.
Related
I have some e-mail attachments being saved to Azure Blob.
I am now trying to write a Azure Functions App that would connect to that blob storage, run some scripts and re-save the file.
However, when selecting a storage account for the function, I couldn't select my blob storage account.
I went on the website and it said this:
When creating a function app, you must create or link to a general-purpose Azure Storage account that supports Blob, Queue, and Table storage. Some storage accounts don't support queues and tables. These accounts include blob-only storage accounts and Azure Premium Storage.
I'm wondering, is there any workaround this? and if not, perhaps any other suggestions? I'm becoming a little lost in all the options, and which one to actually choose.
Thanks!
EDIT: Might I add I writing the function Python
I think you are overlooking the fact that you can have multiple storage accounts. In order for an Azure Function to work you need a storage account. That storage account is used to store runtime information of the Azure Function for internal purposes like state management. This storage account is subject to restrictions as you already found out. There is no workaround for that.
However, if the function you are writing needs to access another storage account it is free to do so. You just have to provide details to connect to that specific storage account. In that case you also have a clear seperation between the storage account that is used by the azure function for its internal operations and the storage account your application needs to connect and which you have total control about withouth having to worry that you break things by deleting internal used blobs/tables/queues.
You can have a blob triggered function that gets triggered when changes occur on your specific blob storage. That doesn't need to be the storage account that the azure function internally uses, which is created/selected when creating the azure function.
Here is a sample that shows how to add a blob triggered azure function in Python. MyStorageAccountAppSetting refers to an app setting that holds the connection string to the storage account that you use for storage.
The snippet from the website you are quoting is for storing the function app code itself and any related modules. It does not pertain to what your function can access when the code of your function executes.
When your function executes it will need to use the Azure Blob Storage SDK/modules to connect to your blob storage account and read the email attachments. Here's a quickstart guide for using Azure Storage with Python: Quickstart with Azure Storage Blobs SDK for Python
General-purpose v2 storage accounts support the latest Azure Storage features and incorporate all of the functionality of general-purpose v1 and Blob storage accounts here
There are more integration options with GPv2 accounts including Azure Function Triggers. See: Azure Blob storage bindings for Azure Functions
Further refer: Types of storage accounts
If Blob, based on your need, you can choose an access tier based on the frequency of access for the data (e-mail attachments)Access tiers for Azure Blob Storage - hot, cool, and archive. If General purpose storage account, its standard performance tier.
Is there any way to find out on our own where the ingress/egress activities are originating from/to (at least some details) for Azure Storage account?
Is there any way to find out on our own where the ingress/egress
activities are originating from/to (at least some details) for Azure
Storage account?
You should be able to find this information out by analyzing contents of $logs blob container in your storage account. This blob container contains Storage Analytics Logs. You may need to enable storage analytics logging for your storage account as I believe it is not enabled by default.
You can find more information about storage analytics logging here: https://learn.microsoft.com/en-us/azure/storage/common/storage-analytics-logging?tabs=dotnet.
Our software uses Azure blob & Azure table storage.
I would like developers to be able to look through our production data with the Microsoft Azure Storage Explorer, but not be allowed to accidentaly edit it's data.
I don't want to allow anonymous access to the data (read only) as suggested here.
What would be a good way to achieve this?
Make use of Shared Access Signature option to connect to Azure Blob Storage from the Storage Explorer.
Find more details about SAS here.
Find more details about SAS in Storage Explorer here.
I'm trying to enable the monitoring tiles in my Azure Storage account, but for the life of me can't get it to work. It keeps coming up with the error"monitoring may not be enabled. Please turn on diagnostics".
I've tried ticking all the checkboxes under Settings->Diagnostics->Monitoring but nothing seems to work.
Is there a trick I'm missing?
Are you trying to monitor a Premium Azure Storage account? I dont believe those can be monitored at this time, as monitored/analytical data for them is stored in Table Storage and Premium Storage accounts do not support Table Storage or Queue storage.
Someone explain to me what it is and how the Windows Azure Storage Analytics works and how I can use it in conjunction with storage.
Windows Azure Storage Analytics offers profiler like capabilities for Azure Storage (which includes Tables, Blobs and Queues).
You can find a very good overview of Azure Storage Analytics directly on MSDN. Then, for digging deeper and also getting some code samples, you can go here related to the logging functionality and here for the metrics one.
Check out the new Windows Azure Storage Analytics App for Windows 8 in the app store:
http://apps.microsoft.com/windows/en-US/app/azure-storage-monitor/e9292e05-c469-403d-a787-63645b861593