For incremental backups using Azure MySQL server
You can protect Azure MySQL server assets with a protection plan and policy. You can use full and differential-incremental schedules at the instance level. The individual databases can only be protected using the full schedule.
You can recover individual databases from the backups of a server taken to another destination server. Restore fails if a database with the same name exists on the destination server.
Currently, NetBackup does not restore the users and their permissions to the destination server. All database objects are recovered with the same users as in the source database during the time of the backup. You can create users and grant the necessary permissions, after restore.
Records in the tables created with storage engine type MEMORY are not backed up during an incremental schedule. These records remain in memory, and changes made to those tables do not reflect in the binary logs.
NetBackup performs a full backup during an incremental schedule in the following scenarios:
One or more binary logs on the server are purged between the subsequent incremental backups. Ensure that the binlog_expire_logs_seconds value is set to the appropriate value based on the frequency of the incremental schedule.
If you change the schema of one or more databases on a server and then perform any DDL action on any of those databases.
One or more databases are added or removed from the server.
If the server is configured as High Availability, and a failover occurs on the server.
If the asset's maximum incremental recovery points criteria (100) is reached under the subscribed policy or protection plan.