Bug #7660 START BACKUP does not increment BACKUP-ID
Submitted: 4 Jan 2005 13:25 Modified: 11 Jan 2005 12:49
Reporter: Johan Andersson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1.9 src OS:HP/UX (HP-UX hpita2 B.11.23 U ia64)
Assigned to: Tomas Ulin CPU Architecture:Any

[4 Jan 2005 13:25] Johan Andersson 
Description:
START BACKUP does not increment BACKUP-ID:

Node 2: Backup 0 started from node 1
Node 2: Backup 0 started from node 1 completed
 StartGCP: 38 StopGCP: 50
 #Records: 32165 #LogRecords: 3577
 Data: 87514824 bytes Log: 10025532 bytes

Subsequent backups also have BACKUP-ID = 0.

This yields unusable BACKUPs since they cannot be restored (BACKUP-ID must not be 0 in ndb_restore).  

Temp fix can be to remove that check in ndb_restore, because then it is possible to restore the backups.

Note, I have only seen this problem in HP-UX, and there is no probs on Linux.
(On HP-UX, the aCC compiler was used).

How to repeat:
ndb_mgm> START BACKUP 

Suggested fix:
The problem is in 
  ptr.p->backupId = conf->sequenceValue[0]; 

in Backup.cpp.   It always return 0; so maybe this can be in many places where the UtilSequenceXXX is used.
[11 Jan 2005 12:49] Tomas Ulin 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html