Shulou(Shulou.com)06/02 Report--

This time to talk about the topic of backup, the importance of backup needless to say, this time to talk about how to do backup on the cloud. We all know that PaaS services are lighter and easier to manage, and one of the most important points is that the backup of PaaS services is often very simple. Most of the time, the backup strategy is set with a click of the mouse, and some of them are even backed up automatically in the background. Take the MySQL of Azure SQL and Azure, the backend automatically makes regular backups without our care at all, but how to back up the database running in VM? We can use recovery service to make virtual machine backups, which is no problem, of course, but without regular log backups at the database level, the log size of the database will continue to grow.

Therefore, it is useless to rely on VM level backup alone. We must do database level backup. The traditional method is to use third-party tools or database job, maintenance plans and other methods to do regular backups. Of course, this method can also be used in the cloud, but a big pain point of this method is that we have to maintain these backed-up data ourselves, which is very painful.

Azure provides an easy way for us to back up SQL Server databases. This method has been available for a long time in Azure Global, but it was not until this month that we finally landed on 21V Azure! We can now back up the database directly in recovery service vault!

Previously, we can only back up VM in recovery service vault, but now we can also use it to back up SQL Server database. And it supports many versions, from SQL Server 2008 R2 to the latest version of SQL Server, but SQL Server under linux does not support it yet.

Let's take a look at the steps of the operation.

First create a recovery service vault

Then select backup SQL Server in Azure VM in backup, and then select start discovery

You can see that we have found our server. Start discovery dbs.

Start to configure db backup after completion

At this point, you may find here a hint of not ready.

Why is that? The reason is very simple, because our SQL Server is not created from marketing place, but we deploy VM first, and then install SQL Server independently, so we still need to complete some steps manually. We can see that it is already obvious in the error message that backup cannot be made because of insufficient account permissions.

In fact, the principle of Backup is not complicated. It uses extension to call some backup API in VM to backup the database, so it is equivalent to executing the command in VM, and the account needed to execute the command is seen in the error message above.

Go to VM and create a new database login directly.

Search for an account called AzureWLBackupPluginSvc

Grant this account sysadmin permission

You can see the permissions.

Go back to the previous page and re-discovery dbs

After re-discovery, the status is already ready

To start configuring backup, select autoproject as On, which means that all current databases and databases added in the future will be backed up automatically

Uninstall the backup strategy, which is very similar to VM backup

It is set here to do everything every day, and the data will be retained for 30 days.

After that, you can see that some databases have shown that the backup status is health. Try restore this time.

Here you choose to restore to the current server, and then change the name to another

You can also set the location of data and log

After the setup is complete, you can see that the database will be restored soon.

The backup data cannot be seen on the hard disk, because the data is encrypted and stored in recovery service, so we no longer have to worry about the disk being propped up by the backup data.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.