Backup Fails With Error "Backup log buffer full" When Running High Traffic (Doc ID 2016150.1)

Last updated on NOVEMBER 24, 2015

Applies to:

MySQL Cluster - Version 7.2 to 7.4 [Release 7.2 to 7.4]
Information in this document applies to any platform.


Backup fails with "log buffer full" error:

Starting Backup ...
Launching order Backup for grp1 in group 1.
Obtaining Mgm Information.
Trying backup on mgmt access 1, wait a moment ...
ndb_mgm 2372 -e "START BACKUP 999 WAIT COMPLETED"
Error in server MGM:, store grp1: Connected to Management Server at:
Waiting for completed, this may take several minutes
Backup failed
*  3001: Could not start backup
*        Backup log buffer full: Permanent error: Internal error.
BACKUP-999 renamed in PL_2_7 to /mysql/ndbd/backup/BACKUP/BACKUP-999_OLD_2014-11-24_12-19
BACKUP-999 renamed in PL_2_8 to /mysql/ndbd/backup/BACKUP/BACKUP-999_OLD_2014-11-24_12-19

In Cluster log can be seen the following error:

2014-01-27 11:25:08 [MgmtSrvr] ALERT    -- Node 3: Backup 999 started from 1 has been aborted. Error: 1324
2014-01-27 11:25:09 [MgmtSrvr] ALERT    -- Node 3: Backup request from 2 failed to start. Error: 1302


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms