A transaction log backup captures the transaction log that contains a record of all committed or uncommitted transactions. Transaction log backups are consistent with the start time of the backup.
Transaction log backups make point-in-time recovery possible. This is useful in the case of a database failure where it is unacceptable to lose any data, and you want to restore to the point of failure. If you use only full backups, you can restore to the time of the backup, but not to a point-in-time between backups.
A transaction log backup is similar to a traditional incremental backup that you might perform on a file system because the transaction log backup contains only the new changes since the full or another transaction log backup.
Each time a transaction log is backed up, it is truncated to the exact time of the backup. No checkpoint is issued at this time; therefore, dirty pages are not written to disk before or after a transaction log backup. If there are dirty pages (pages that are changed and not yet added to the database files), any completed transactions must be rolled forward if a transaction log restore is performed. Any transactions that are not completed at the time a transaction log backup is performed are rolled back during a restore involving a transaction log backup.
Before You Begin
-
Enable binary logging on the MySQL Server.
-
Set the MySQL Server system variable expire_log_days to 0 to make sure that the logs are not pruned by the MySQL Server automatically.
Procedure
-
From the CommCell Browser, navigate to Client Computers > client > MySQL > instance.
-
Right-click a subclient, and then click Backup.
-
In the Select Backup Type area of the dialog box that appears, select Incremental as the backup type.
-
In the Job Initiation area, select Immediate to run the job now.
-
Click OK.
You can track the progress of the job from the Job Controller. When the backup is complete, the Job Controller displays Completed.