Bug #17520 restore operation from a backup of release -x aborts
Submitted: 17 Feb 2006 9:26 Modified: 17 Mar 2006 9:34
Reporter: patrice audigou Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:5.1.6-alpha OS:Linux (RedHat9)
Assigned to: Assigned Account CPU Architecture:Any

[17 Feb 2006 9:26] patrice audigou
On a cluster at release 5.1.6-alpha , the restore operation aborts if i
try to restore a backup that has been done on a cluster at release 5.1.2-a_drop5p8.
-Clusters are identical (config.ini,my.cnf)
- I applied the patch  http://lists.mysql.com/commits/2583 on 5.1.6-alpha release

on 5.1.2-a_drop5p8 station
-The backup operation is done with ndb_mgm using the "start backup"
-The backup is transfered via ftp on the 5.1.6-alpha machine.

on 5.1.6-alpha machine
-The ndb node is started with the --initial option
-The following restore operation is launched

 "/usr/mysql/bin/ndb_restore --ndb-connectstring=host=xxxx:2200
--backupid=1 --nodeid=2 --restore_data --print_log /.../BACKUP/BACKUP-1" 

the restore operation aborts with the following error message

  "Processing data in table: hlr/def/IMSI(3) fragment 0"

How to repeat:
"/usr/mysql/bin/ndb_restore --ndb-connectstring=host=xxxx:2200
--backupid=1 --nodeid=2 --restore_data --print_log /.../BACKUP/BACKUP-1"
[17 Feb 2006 9:27] patrice audigou

Attachment: createtableNew.sql (text/x-sql), 200 bytes.

[18 Mar 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".