Sorry - haven't had a chance to respond till now. > > So "restore" == "apply-log", but one works on any computer, and the other > > only works on the computer that it's node locked to.
> --apply-log works also in any computer regardless of the hostname or the > license expiration date. I'm running ibbackup on an unlicenced machine. The manual states, "ibbackup --apply-log /home/pekka/.backup-my.cnf" Here's the output with --apply-log (some sensitive info stripped) ------------------------------------------------------- mydb2:/data # ./ibbackup --apply-log ./my2.cnf InnoDB Hot Backup version 1.40; Copyright 2003 Innobase Oy License xxx is granted to (--restore works in any computer regardless of the hostname) Licensed for use in a computer whose hostname is 'hrdb1' Expires 2005-6-1 (year-month-day) at 00:00 See http://www.innodb.com for further information Type ibbackup --license for detailed license terms, --help for help --- Error: the hostname of this computer is 'mydb2'. Please contact [EMAIL PROTECTED] for a license renewal. -------------------------------------------------------- If I run with --restore, however (same directory, same files, 30 seconds after the above command was run), -------------------------------------------------------- mydb2:/data # ./ibbackup --restore ./my2.cnf InnoDB Hot Backup version 1.40; Copyright 2003 Innobase Oy License xxx is granted to (--restore works in any computer regardless of the hostname) Licensed for use in a computer whose hostname is 'hrdb1' Expires 2005-6-1 (year-month-day) at 00:00 See http://www.innodb.com for further information Type ibbackup --license for detailed license terms, --help for help Contents of ./my2.cnf: innodb_data_home_dir got value /data innodb_data_file_path got value ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata 4:100M:autoextend innodb_log_group_home_dir got value /data innodb_log_files_in_group got value 2 innodb_log_file_size got value 104857600 .... .... ibbackup: We were able to parse ibbackup_logfile up to ibbackup: lsn 5 2076170601 040514 9:51:43 ibbackup: Full backup restoration successful! ----------------------------------------- Am I doing something wrong with regards to --apply-log? > Looks like you have taken the backup with ibbackup-2.0, but are trying to > run --apply-log with ibbackup-1.40. You should use the same or later > ibbackup version to run --apply-log. Maybe you have forgotten to replace > your old ibbackup-1.40 binary with the new ibbackup-2.0 binary, and the > innobackup script is using the old binary? That's a possibility - we were using a demo-ibbackup for a month or two, before ordering the full version - I guess the demo was beta, and the licenced version was 1.4. There is no version # in the name of the file, and I didn't think to check the version by running with the --help flag. I tried with a more recent backup, and it worked (as you can see above). > That is safer. It can reveal corruption. > > > Or is it only done if you need > > to use the backup? > > --apply-log is needed to use the backup. But I recommend doing it > immediately after you have taken the backup. > > In short, the logic is this: > > 1. Take a backup. > 2. Run --apply-log to make the backup a 'consistent snapshot'. > 3. Use the backup. Ok - thx - that makes sense. David. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
