We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.
Anyone from the MS teams care to comment?
I'd like to throw my hat in here and second everything mentioned below. This is really a critical omission and needs to get sorted ASAP.
Makes sense! Let us know which specific recommendations you’d like to see and vote this up to let us know how important it is for you.
It would be great if cloudyn could run a utilisation check on app services plans and come with suggestions on scaling up-down ( or in and out) depending on usage.
And maybe come with specific recommendations, like perhaps scheduled scaling ( i. e scale down between 10 pm and 05 am) and other cost vs performance suggestions.
We have bumped into scenarios where we could really use a short term bump on something within the basic tier, but are then ether forced to migrate the contents to a GP scaled mysql or suffer the CPU limit.
The alternative is not really much better due to the fact that we do have some low intensity DB's that have peak load on certain days /dates, but barely use 20 % in the "off period"
It would be fantastic to be able to scale to and from basic or at least scale GB down to a single core
Audit logging for Azure Database for MySQL is now available in preview. Audit logs are integrated with Azure Monitor Diagnostic Logs. To learn more, please check out the following doc: https://docs.microsoft.com/en-us/azure/mysql/concepts-audit-logs
Support for up to five read-only replicas within the same region is now in public preview. This feature is aimed to scale out read-heavy workloads.
Check out the documentation to learn more about replicas:
- Overview: docs.microsoft.com/en-us/azure/mysql/concep..
- How to create replicas from the portal: docs.microsoft.com/en-us/azure/mysql/howto-..
Azure CLI support will be following shortly.
Andrea Lam on behalf of the Azure Database for MySQL product team
This would be awesome to have!
Currently there is support available for backing up System State using just the MARS Agent to recover to the same/similar hardware in case of server or software malfunction.
We wanted to understand the scenarios where a full server recovery cannot be achieved using Azure Site Recovery. Please share your feedback so we can review and plan this accordingly.
Exclude disk functionality for Write accelerator(WA) enabled disks is available now. No action is required from the user. During VM backup, Azure backup service automatically excludes the WA enabled disk and backs up the rest of the disks in a VM.
495 votesunplanned · 18 comments · Azure Backup » Retention and Storage · Flag idea as inappropriate… · Admin →
Great feedback that is currently under review
Thank you for the feedback. The product team is aware of this need and will consider it if resourcing allows.
Thank you for your feedback. In the meantime you can create an error action on the job that is configured to send an email via a service like SendGrid or a text message via a service like Twilio.
Thank you for the suggestion. We are working on a solution that we hope will be delivered in this calendar year.
Thanks for the feedback! We are working on enabling this feature.