Backup Azure PaaS resources
Backup any Azure PaaS resource using Azure Backup. Please comment with resources you are looking backup support for.
We have initiated the work on enabling backup for blob storage and is underway, ETA: H1CY20.
For more details, please reach out to AskAzureBackupTeam@microsoft.com
Raf Nijs commented
Azure Database for MySQL server
Appservice => functions in consumtion plan
Storage accounts, key vault, Azure DNS
Key vault, storage accounts, vmss, config backups for vnet/LBs, automation accounts
Klaus g. Nielsen commented
Storage accounts is Much needed
Fernando Sola commented
Automation accounts, Azure DNS, Storage Blobs
Alex Khassanov commented
Automation Accounts, Storage Accounts
Hélder Pinto commented
Critical: Storage (Blob, File, Table)
Nice to have: App Service, Azure SQL Database, Azure Database for MySQL/PostgreSQL
Thomas Janetscheck commented
Azure Key Vault
Blob Storage Accounts
David Hyrtl commented
The most important PaaS backup we need is for Storage Accounts. For example for Web Apps which store data in blob containers.
Orin Thomas commented
Azure DW - because you can back up/export an Azure DB, but not a DW DB
Christian Forjahn commented
Sorry flagged it as inappropriate by accident.
We need backup for any PaaS that includes data.
Gururaj Pandurangi commented
1) All Azure DB (SQL DB, SQL DW, CosmosDB, SQL Stretch DB,...)
2) Azure Key Vault
3) Azure file storage - a version management (last X versions) will be great
4) Azure Monitor - especially alerts, most of the team is used to creating alerts on the portal and forget about it. Not very repeatable for recreating in multiple environments.
5) Azure web Apps - especially Wordpress apps.
6) Runbooks - Would be great to have a version management built into it (e.g. last X changes)
Adin Ermie commented
Web Apps, Azure SQL, Azure Automation Runbooks/schedules, Azure Monitor custom created Alers
Is this item asking for Storage backup? I often struggle with this myself. We allow backup of Page Blob through VM backups where they use unmanaged disks, but what is the best practice for backing up a Storage Account and what does Azure offer as guidance here. I saw a Storage Account "Recycle bin" feature request which will be great to cover accidental deletion, and I suppose if I have 30 days retention, that could also cover corruption which got replicated across regions. Maybe that is the answer here?
Felix Bodmer commented
Considered different options to implement Azure Table backup (Scripting, Azure Data Factory ...). They all work, but none of them are satisfactory, particularly from an operational point of view. Would like to cover both protection against data loss and logical corruption (e.g. accidental deletion). Using Azure Backup would be the ideal solution.
Cuauhtemoc Tello commented
We have a use case for backing up Azure tables at the moment, but this topic has been under review for +2 years. How realistic is it that we see this feature in 2017?
Richard Knott commented
Seconded, especially Azure File storage. At the moment a VM needs to be spun up (or 2 to be safe), and a batch file using AZCOPY to take a frequent copy, then a backup with Azure Backup. It's not exactly the most efficient use of resources and storage.
Surely this has been partially done using the azure storage API to provide VM backups? How else does it get the vhd blobs?
Oliver Hamou commented
Yes, please add backup support, with quantity days like Sql Azure.
it' s important if you have an error on disk or delete by user.
This you can do from "Cloudbacko Pro" software because with "Cloudbacko Pro" you can take Multi-destination concurrent backup for Microsoft SQL Server also. Leaving a link below just check: http://www.cloudbacko.com/sql-backup.jsp
Martin Edelius commented
We're in the process of offering Azure File Services for our end user as this would allow them to distribute files all over the world in a controlled, reliable manner.
In order to provide this as a service we need to be able to provide more protection than the DR-capabilities built into Azure, for example if a user by mistake deletes a file or folder.
I'm thinking that there'd be a backup operator role in the RBAC that we can assign to the resource group containing the Azure File Service. Users with this role can through the Azure Backup UI configure backup and restore policies for objects in the Azure File Service and also backup and restore the actual objects. No direct access to the objects is given through this role though.