MySQL Bugs: #18935: restore of apply_status table fails using old ndb backup

Bug #18935	restore of apply_status table fails using old ndb backup
Submitted:	10 Apr 2006 8:44	Modified:	26 Apr 2006 10:58
Reporter:	patrice audigou	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.8.beta	OS:	Linux (redhat9)
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
Slave synchronization with backup from release  5.1.2-a_drop5p11 does not work.

command used is 
============
/usr/mysql/bin/ndb_restore -e --backupid=1 --nodeid=3 --restore_data /tmp/bk/BACKUP-1

we got the following message : 
=====================

Backup Id = 1
Nodeid = 3
backup path = /tmp/bk/BACKUP-1
Ndb version in backup files: Version 5.1.2
Connected to ndb!!
Unable to find table: apply_status
Restore: Failed to restore table: cluster_replication/def/apply_status ... Exiting
 
NDBT_ProgramExit: 1 - Failed
 

How to repeat:
/*-*/

Hi Patrice,

For the release version of 5.1 we decided to use the database cluster instead of cluster_replication.

You can choose from the below:
A. compile to use the "old" name cluster_replication (we would probably have to do the change for you)
B. we add an option to convert cluster_replication -> cluster (in the restore program + slave), and your newer versions of applications adopt to the new name.

BR,

Tomas

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/5396

pushed to 5.1.10

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

Additional info:

Documented bugfix in 5.1.10 changelog; closed.