Backup Azure Database for MySQL to a Blob Storage

Thanks for this info. It was very helpful. I am dumping a database that is 30,813.1MB in size. On my first try it resulted in a 1,023.27GB file, which seems way too small. Upon inspecting and restoring the file on my local instance of MySQL, I see that the dump stopped midway thru and didn't export all of the tables. On my second try (with -v, to see what might have happened), I got verbose output but I see no errors. I also see mention of one of the tables that was not included in the resulting .sql file. 

Also, the CloudShell times out before it is complete. How can I stop that from happening? I tried pressing backspace every now and then and I think its preventing the timeout but successive runs are not taking more than 20 mins now. 
The file share that was created has a quota of 6GiB. If my dump file exceeds that, what will happen?

Edit: I had Azure Storage Explorer open and the file share selected when doing the dump previously. I closed it, wondering if it was doing something that was interrupting the mysqldump. The MySQL dump took much longer next time. Over an hour and pressing backspace every now and then prevented the CloudShell timeout. The CloudShell finally timed out on me anyway after running for a total of 1 hour, 37 minutes. I will check Azure Storage Explorer for the results tomorrow morning. 

Edit2: The resulting file is still too small: 1,023.19MiB. Its like there is a 1GB limit. The backup does not contain anywhere near all of the data that it should. 

Thank you for the information. I would also suggest zipping the file for a smaller download.
For this post, it could be 

zip -q test_backup test_backup.sql

Joel Hazelton  Sorry for the delayed response, please take a look at this blog post: 

https://techcommunity.microsoft.com/t5/azure-database-for-mysql/steps-to-automate-backups-of-your-azure-database-for-mysql/ba-p/1791157

dhruv-dat Thanks sir, I fixed the screenshot. much appreciate your feedback

 -F, --flush-logs Flush logs file in server before starting dump. Note that if you dump many databases at once (using the option --databases= or --all-databases), the logs will be flushed for each database dumped. The exception is when using --lock-all-tables or --master-data: in this case the logs will be flushed only once, corresponding to the moment all tables are locked. So if you want your dump and the log flush to happen at the same exact moment you should use --lock-all-tables or --master-data with --flush-logs.

-c, --complete-insert: Use complete insert statements.

-v, --verbose Print info about the various stages.

Hello Bashar-MSFT ,

May I know what -Fc and -v are for?

Bashar-MSFT Please have the image corrected and hmikhan your comment updated.

For mysqldump, -d option is not used to specify database name. -d, --no-data No row information. This is used to take a dump of the database without any data.

-B is the option that should be used.

Thank you for the useful article. It looks like this method leverages the cloud storage that is created when you run code from Azure Cloudshell. I'd like to run this remotely from something like Azure Automation on a regular schedule. Is there a way to use this same method without leveraging Azure Cloud Shell storage?

Ops_Biren , thanks for your comment, restore from Azure Blog Storage should be similar

1- Navigate to your Azure Database for MySQL server on the portal and Run Azure Cloud Shell (Bash).  If you run this for the first time it will ask you to create a Storage container and and this will mount an Azure File in it.

2- Type df in the cloud shell and collect the Azure File path

3- Change directory to the cloud drive using the cd command
     in the example below I used cd /usr/bashar/clouddrive

4- Now that you are in that directory run mysql command,
example: mysql -h mydemoserver.mysql.database.azure.com -u myadmin@mydemoserver -p testdb < testdb_backup.sql

ref: https://docs.microsoft.com/en-us/azure/mysql/concepts-migrate-dump-restore#restore-your-mysql-database-using-command-line-or-mysql-workbench

how can we restore it to our new paaS Database