

What do we mean by this? Imagine your disgruntled colleague decides to delete the entire database. However, bear in mind that replication protects against hardware failures, while backups protects against human errors. Some people think that they don’t need a backup because they have replication. If you are not backing up your MySQL databases yet, you should start doing it before you lose your precious data. If GTIDs are enabled on the instance, SELECT versions 4.1.0 and later, the files themselves are written outside the lock (but the data is retrieved inside the lock to get consistent data).“There are two types of people: people who do backup, and people who will start doing it.”.If the –slave-info option was specified, SHOW SLAVE STATUS.SHOW MASTER STATUS to get the binary log coordinates for the instance being backed up.Create the meta/backup_variables.txt, meta/ibbackup_slave_info, meta/backup_gtid_executed.sql files.

For image backups, copy the InnoDB native symbolic link files (.isl) to the image.Remove dropped InnoDB tablespace files.In MySQL Enterprise Backup 4.1.0 and later, this can be skipped using the –skip-final-rescan option in this case it is your responsibility to ensure no DDL changes are made to InnoDB tables during the backup. Rescan the InnoDB tablespace files for schema changes.

