Overview - MySQL iDataAgent
The MySQL iDataAgent provides a simplified end-to-end backup and recovery solution for MySQL data in your enterprise. The product can be used to perform both full system rebuilds and granular recovery of the data.
The MySQL iDataAgent provides the flexibility to backup the MySQL database from different environments. You can perform a full or incremental backup of the entire instance, individual databases or files and file groups, and the transaction logs at any point of time.
You can backup both the system and user-defined databases. You can perform a comprehensive backup of all of the databases in an instance or schedule backups for the individual databases. In addition, you can auto-discover new databases so that you can manage the backup of all of the databases in your environment comprehensively.
Transaction Log Backups
Transaction log backups captures the transaction log whether the transaction was committed or not. The use of transaction log backups make point in time recovery possible. You can restore to any point in time within the transaction log.
The MySQL iDataAgent provides the ability to recover databases or an entire MySQL instance. There are no mounting, no recovery wizards, no extra steps needed; the software takes care of it all. This includes the following abilities:
- Full or Partial Restore databases
- Restore and replay transaction logs
- Set Database state during restore (Recovery, Standby, No Recovery)
- Point-in-time recovery
You can view and verify the status of backup and recovery operations from the Job Controller and the Event Viewer within the CommCell Console. You can also track the status of the jobs using Reports, which can be saved and distributed. Generate reports for different aspects of data management. Customize the reports to display only the required data and save them to a specific location in different formats. For example, you can create a backup job summary report to view the completed backup jobs.
You can schedule, generate and send the Reports via email without user intervention.
In the event that the MediaAgent used for the backup or recovery operation fails, the backup is automatically resumed on an alternate MediaAgents. In such cases, the backup or restore job does not restart from the beginning, but resumes from the point of failure. This is useful for backups and restores of large amount of file system data.
In the event that a network goes down, the backup and recovery jobs are resumed on alternate data paths. Similarly, in the event of a device failure, the jobs are automatically switched to alternate disk and tape drives.
You can use block-level backup as a faster method to back up data because only the extents (or modified parts of the database) are backed up rather than the entire MySQL database. You eliminate the need to run a full backup each time the database is changed. For more information, see MySQL Block-Level Backup.
Deduplication provides a smarter way to store data by identifying and eliminating the duplicate items in a data protection operation.
Deduplication at the data block-level compares blocks of data against each other. If an object (such as, file, database) contains blocks of data that are identical to each other, then block-level deduplication does not store the redundant data, which reduces the size of the object in storage. This reduces the size of the backup data copies on both the disk and tapes.
The MySQL documentation uses the following terminology:
|The computer on which the iDataAgent is installed and that contains the data to be secured.|
|The MySQL server that is used for backup and restore operations.|
|The MySQL databases within the instance that is used for backup and restore operations.|