MySQL Enterprise Backup Failed When Relay Log is Deleted During Backup
(Doc ID 2163862.1)
Last updated on FEBRUARY 03, 2019
Applies to:
MySQL Enterprise Backup - Version 3.11 to 3.12 [Release 3.11 to 3.12]Information in this document applies to any platform.
Symptoms
MySQL Enterprise Backup (MEB) failed when relay-log-file does not exists.
Using command:
mysqlbackup --backup-dir="${BACKUPDATA}/${CURDATE}" --include-tables="${INCTABLE}" --exclude-tables="${EXCTABLE}" --use-tts backup-and-apply-log &parent=EXTERNAL_SEARCH" rel="nofollow" ${BACKUPLOG}" 2>&1
Following error occurs:
160708 04:05:32 mysqlbackup: INFO: Starting to copy Binlog files...
mysqlbackup: Progress in MB: 2600 2800 3000 3200 3400 3600 3800 4000 4200 4400 4600 4800 5000 5200 5400 5600 5800 6000 6200 6400 6600 6800 7000 7200 7400 7600 7800 8000 8200 8400
mysqlbackup: ERROR: Opening of file /opt/etc/mysql/db/mysql-relay-bin.003824 failed. Error code: 2, No such file or directory
mysqlbackup: Progress in MB: 2600 2800 3000 3200 3400 3600 3800 4000 4200 4400 4600 4800 5000 5200 5400 5600 5800 6000 6200 6400 6600 6800 7000 7200 7400 7600 7800 8000 8200 8400
mysqlbackup: ERROR: Opening of file /opt/etc/mysql/db/mysql-relay-bin.003824 failed. Error code: 2, No such file or directory
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |