_backup.filter changes the way a restore works. To exclude folders and files from being stored in your future backups, create a _backup.filter file in the %HOME%\site\Note You don't want to back up the log files.Your app has over 10 GB of content (that's the max amount you can back up at a time).You set up weekly backups of your app that contains static content that never changes, such as old blog posts or images.Sometimes you don't want to back up everything on your app. Partial backups are supported for custom backups. In the Configure custom backups page, select Set schedule.Ĭonfigure the backup schedule as desired and select Configure. If it fails with an error, you can select the line item to see the error message. The custom backup is displayed in the list with a progress indicator. On-demand backups are retained indefinitely.Īt the top of the Backups page, select Backup Now. Once the storage account and container is configured, you can initiate an on-demand backup at any time. If you make settings for in-app MySQL databases manually, such as adding connection strings, the backups may not work correctly. In-app MySQL databases are backed up always without any configuration.
To back up the linked database(s), select Next: Advanced > Include database, and select the database(s) to back up.įor a supported database to appear in this list, its connection string must exist in the Connection strings section of the Configuration page for your app. In Storage account, select an existing storage account (in the same subscription) or select Create new. In your app management page in the Azure portal, in the left menu, select Backups.Īt the top of the Backups page, select Configure custom backups. For more information, see az webapp config snapshot restore.
To restore app content only and not the app configuration, use the -restore-content-only parameter. To restore the automatic backup to a different app: az webapp config snapshot restore -name -resource-group -source-name -source-resource-group -time To restore the automatic backup by overwriting the app's content and configuration: az webapp config snapshot restore -name -resource-group -time az webapp config snapshot list -name -resource-group In the command output, copy the time property of the backup you want to restore. These CLI steps apply to automatic backups only. The following linked databases can be backed up: SQL Database, Azure Database for MySQL, Azure Database for PostgreSQL, MySQL in-app. The following table shows the differences between the two types.ġ0 GB, 4 GB of which can be the linked database. Custom backups require initial configuration, and can be made on-demand or on a schedule. Automatic backups made for your app regularly as long as it's in a supported pricing tier. There are two types of backups in App Service. For more information about scaling your App Service plan to use a higher tier, see Scale up an app in Azure.
#Sonarr restore backup how to#
This article shows you how to restore a backup and make custom backups.īackup and restore Standard, Premium, Isolated.
You can restore a backup by overwriting an existing app by restoring to a new app or slot. You can also make on-demand custom backups or configure scheduled custom backups. In Azure App Service, you can easily restore app backups.
0 kommentar(er)
