Bug #44557 Cannot restore 5.0 backup in 6.3 cluster
Submitted: 29 Apr 2009 20:12 Modified: 18 Aug 2009 13:39
Reporter: Andrew Hutchings Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3,mysql-cluster-7.0 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[29 Apr 2009 20:12] Andrew Hutchings
When restoring a cluster backup with a specific data structure we get the following.  This happens when the schema is imported from the backup or a dump:

Nodeid = 1
Backup Id = 26
backup path = /home/marjoh/backup/BACKUP-26
Opening file '/home/marjoh/backup/BACKUP-26/BACKUP-26.1.ctl'
Backup version in files: ndb-5.0.77
Stop GCP of Backup: 0
Connected to ndb!!
m_columns port != port
Restore: Failed to restore data, test/def/services table structure doesn't match backup ... Exiting 

NDBT_ProgramExit: 1 - Failed

How to repeat:
Adding to private comment due to customer data
[30 Apr 2009 12:59] Jonathan Miller
Also in mysql-5.1-telco.7.0
[18 Aug 2009 12:50] Jonas Oreland

I think you need to use the "--promote-attributes" to convert from
"fake-varsize" in 5.0 to true varsize in 6.3
[18 Aug 2009 13:39] Andrew Hutchings
Hi Jonas,

You are correct, I missed that, many thanks.  Test now works with that parameter, closing as Not a Bug