Configuring incremental backups for Azure MySQL server
NetBackup supports both full and differential incremental backup schedules for Azure MySQL server. During full backup, NetBackup takes a logical dump of all user databases. During incremental backups, NetBackup downloads the binary logs generated on the MySQL server between subsequent incremental backups. When you restore a database, NetBackup creates the database with the full backups and then applies the binary logs in chronological sequence.
Configure the following parameters in the Azure portal.
Table: Parameters for incremental backup
Parameter | Description | Recommendation |
|---|---|---|
| Number of seconds to wait before the binary log file is purged. | This value must be higher than the frequency of backups in the schedule. Ensures that the binary logs on the server are not purged between subsequent incremental backups. |
| The status of binary logging on the server, either enabled (ON) or disabled (OFF). | For incremental backups, this parameter must be set to ON. It captures the changes in the binary log file. |
| This variable applies when binary logging is enabled. It allows the stored function creators to be trusted to make stored functions that allow unsafe events to be written to the binary log. | To restore databases to servers, set this parameter as ON. |
| Specifies the default encryption setting to use for the schemas and general tablespaces, when they are created without specifying an ENCRYPTION clause. | To restore databases to servers, set this parameter as ON. |
| If a transaction requires more memory than this specified value, the server generates a storage error. | Ensure that this value can accommodate the maximum total size of a transaction. We recommend keeping the default value of this parameter. |