Re: innodb backup
I'm interested in InnoDB backups. Does anyone use PHPMyAdmin ? I've a MySQL server on a shared hosting server. Cheers Neil On Sat, Oct 9, 2010 at 3:21 AM, short.cut...@yahoo.com.cn wrote: Hello, Is there any good document for backup of InnoDB? includes the increment backup and full backup. Thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=neil.tompk...@googlemail.com
Re: innodb backup
Hi, On Sat, Oct 9, 2010 at 4:21 AM, short.cut...@yahoo.com.cn wrote: Hello, Is there any good document for backup of InnoDB? includes the increment backup and full backup. There is an overview of backups here http://dev.mysql.com/doc/refman/5.1/en/backup-methods.html XtraBackup supports incremental backups for InnoDB/XtraDB. http://www.percona.com/software/percona-xtrabackup/ Ewen Thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=ewen.fort...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
innodb backup
Hello, Is there any good document for backup of InnoDB? includes the increment backup and full backup. Thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Problem with InnoDB backup
Hi! I have copied all the files from mysql/data folder and burned them on CD. Then i've formated old hard drive. Now i'm trying to copy them back on the fresh mysql installation. Unfortunately after I copy iblogs and ibdata1 mysql is not working anymore. What I can read in error log file is: InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485760 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 050914 0:58:54 Can't init databases 050914 0:58:54 Aborting Now, when I have corrected log file size in my.ini, I got this: InnoDB: No valid checkpoint found. InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Error_creating_InnoDB.html 050914 1:13:20 Can't init databases 050914 1:13:20 Aborting 050914 1:13:22 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 050914 1:13:22 MySQL: Shutdown Complete Anyone know how to fix this error? Is it possible to get my data back? Best regards, Wojciech 'gulldarek' Zylinski -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: memory error innodb backup
Baba, - Original Message - From: Baba Buehler [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Friday, April 29, 2005 12:54 AM Subject: memory error innodb backup We've got a customer whose system has been experiencing corruption in their InnoDB tables. They have returned the system to us and after testing we've determined that the server has bad RAM. This is the same system I had posted about in http://lists.mysql.com/mysql/180785 Memtest86+ v1.55 can run anywhere from 12-24 hours before it picks up any memory errors, so the problem with the memory (or memory subsystem) is very intermittent. the problem might also a bug in the OS or its drivers. Not necessarily bad RAM. We have shipped this customer a replacement server and they have restored their database from a backup that was made with the InnoDB hot backup utility (ibbackup, 1.40). They are now experiencing corruption in their database again on the new system. My question is this: Is it possible that the backup made from the system with the failing RAM is itself corrupted somehow? If there was a corrupt page in the tablespace, would it generate an error during the ibbackup run? Would the restore process be able to If there is a page checksum error, ibbackup will refuse to make a backup. Does the mysqld .err log show page checksum errors? How does the corruption exhibit? uncover an error within the backup? Or is it possible that a corrupted page could survive through the backup/restore process and not be uncovered until it was accessed on the new system? thanks, baba -- Baba Buehler - NetBotz, Inc. - [EMAIL PROTECTED] Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL Network from http://www.mysql.com/network/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
memory error innodb backup
We've got a customer whose system has been experiencing corruption in their InnoDB tables. They have returned the system to us and after testing we've determined that the server has bad RAM. This is the same system I had posted about in http://lists.mysql.com/mysql/180785 Memtest86+ v1.55 can run anywhere from 12-24 hours before it picks up any memory errors, so the problem with the memory (or memory subsystem) is very intermittent. We have shipped this customer a replacement server and they have restored their database from a backup that was made with the InnoDB hot backup utility (ibbackup, 1.40). They are now experiencing corruption in their database again on the new system. My question is this: Is it possible that the backup made from the system with the failing RAM is itself corrupted somehow? If there was a corrupt page in the tablespace, would it generate an error during the ibbackup run? Would the restore process be able to uncover an error within the backup? Or is it possible that a corrupted page could survive through the backup/restore process and not be uncovered until it was accessed on the new system? thanks, baba -- Baba Buehler - NetBotz, Inc. - [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB backup + replication problem?
Hi! Guilhem has now fixed this bug to 4.0.22. Best regards, Heikki Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL support from http://www.mysql.com/support/index.html .. From: Don MacAskill ([EMAIL PROTECTED]) Subject: InnoDB backup + replication problem? This is the only article in this thread View: Original Format Newsgroups: mailing.database.myodbc Date: 2004-09-29 09:58:02 PST I've got an interesting (well, I think so anyway) problem with my replication. The slave chugs along just fine, then spits out: Query caused different errors on master and slave. Error on master: 'Can't execute the query because you have a conflicting read lock' (1223), Error on slave: 'no error' (0). Default database: 'mysql'. Query: 'BEGIN' I check the master binlog position, and discover this: /*!40019 SET @@session.max_insert_delayed_threads=0*/; # at 35294588 #040929 2:25:51 server id 1 log_pos 35294588 Query thread_id=7830089 exec_time=0 error_code=1223 use mysql; SET TIMESTAMP=1096449951; BEGIN; # at 35294629 #040929 2:25:44 server id 1 log_pos 35282293 Query thread_id=7830089 exec_time=0 error_code=0 SET TIMESTAMP=1096449944; INSERT INTO ibbackup_binlog_marker VALUES (1); # at 35294710 #040929 2:25:51 server id 1 log_pos 35294710 Query thread_id=7830089 exec_time=0 error_code=1223 SET TIMESTAMP=1096449951; COMMIT; I didn't see this prior to 4.0.21 (I was on 4.0.20), but it may or may not be related. This has happened a few times now, and always around the time that I finish an InnoDB backup. Anyone else seen this? Any ideas? Thanks, Don -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB backup + replication problem?
I've got an interesting (well, I think so anyway) problem with my replication. The slave chugs along just fine, then spits out: Query caused different errors on master and slave. Error on master: 'Can't execute the query because you have a conflicting read lock' (1223), Error on slave: 'no error' (0). Default database: 'mysql'. Query: 'BEGIN' I check the master binlog position, and discover this: /*!40019 SET @@session.max_insert_delayed_threads=0*/; # at 35294588 #040929 2:25:51 server id 1 log_pos 35294588 Query thread_id=7830089 exec_time=0 error_code=1223 use mysql; SET TIMESTAMP=1096449951; BEGIN; # at 35294629 #040929 2:25:44 server id 1 log_pos 35282293 Query thread_id=7830089 exec_time=0 error_code=0 SET TIMESTAMP=1096449944; INSERT INTO ibbackup_binlog_marker VALUES (1); # at 35294710 #040929 2:25:51 server id 1 log_pos 35294710 Query thread_id=7830089 exec_time=0 error_code=1223 SET TIMESTAMP=1096449951; COMMIT; I didn't see this prior to 4.0.21 (I was on 4.0.20), but it may or may not be related. This has happened a few times now, and always around the time that I finish an InnoDB backup. Anyone else seen this? Any ideas? Thanks, Don -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
hot innodb backup options
All, I have a database where the tables are InnoDB. I am working on the backup procedure, and would like to implement a process where the database is backed up without having to shut it down (live, or hot backup). Reading the documentation, it appears the only option I have is to purchase a solution from InnoDB ($500/yr). Is there a free option out there to do this? Thank you, Kevin Williams -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: hot innodb backup options
this is just my $0.02, but I would think $500/yr is certainly worth it. you'll get a fully supported product, and the money goes to a good cause. jeff Kevin Williams wrote: All, I have a database where the tables are InnoDB. I am working on the backup procedure, and would like to implement a process where the database is backed up without having to shut it down (live, or hot backup). Reading the documentation, it appears the only option I have is to purchase a solution from InnoDB ($500/yr). Is there a free option out there to do this? Thank you, Kevin Williams -- Jeff Mathis, Ph.D. 505-955-1434 The Prediction Company [EMAIL PROTECTED] 525 Camino de los Marquez, Ste 6http://www.predict.com Santa Fe, NM 87505 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: quot;hotquot; innodb backup options
Anonymous wrote on Mon, 01 March 2004 13:26All, I have a database where the tables are InnoDB. I am working on the backup procedure, and would like to implement a process where the database is backed up without having to shut it down (live, or hot backup). Reading the documentation, it appears the only option I have is to purchase a solution from InnoDB ($500/yr). Is there a free option out there to do this? Thank you, Kevin Williams Well, $500 is not bad for a hot backup solution. That being said you can use mysqldump with the --single-transaction option to achieve the same effect, but it will be slower and (probably) take up more storage space. You should also make sure you are using a recent version of mysql or make sure to disable foreign key checks before doing your restore as mysqldump does not back-up the tables with concern for the integrity constraints. -- Regards, Mike Hillyer Webmaster/Moderator http://www.vbmysql.com Read my blog at: http://www.vbmysql.com/mike/blog -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB backup - the best way.
Alternatively, use InnoDB Hot Backup: http://www.innodb.com/hotbackup.html This will let you take a real-time backup of your InnoDB tables without taking the server down. Chris Rafal Jank wrote: Dnia Wed, 28 May 2003 12:57:59 +0200 Jarek Jarzebowski [EMAIL PROTECTED] zezna/a co nastpuje: Hi, I have MySQL 4.0.12 working on Debian Linux box. DB server uses MYISAM and InnoDB tables. MySQL docs shows what is the best way to backup InnoDB tables but I don't want to shutdown db server every backup time. I suppose it is not a good idea to just copy database files and innodb log files to the safe place because of unwanted rollbacks danger. What if I use mysqldump to backup databases data, and then I copy innodb log files to the safe place? I suppose I should flush tables first. You can mysqldump InnoDB tables too. Copying InnoDB files (data or redologs) without shuting down mysql is a bad idea. You can also use mysql replication if you have spare server and do a cold backup from it. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB backup - the best way.
On Wed, May 28, 2003 at 09:53:02AM -0700, Chris Tucker wrote: Alternatively, use InnoDB Hot Backup: http://www.innodb.com/hotbackup.html This will let you take a real-time backup of your InnoDB tables without taking the server down. Agreed. Aside from shutting down MySQL and backing it up with your favorite backup too, the hot backup tool is the best option. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.8: up 114 days, processed 3,574,938,408 queries (360/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB backup - the best way.
Hi, I have MySQL 4.0.12 working on Debian Linux box. DB server uses MYISAM and InnoDB tables. MySQL docs shows what is the best way to backup InnoDB tables but I don't want to shutdown db server every backup time. I suppose it is not a good idea to just copy database files and innodb log files to the safe place because of unwanted rollbacks danger. What if I use mysqldump to backup databases data, and then I copy innodb log files to the safe place? I suppose I should flush tables first. I'm interested in your opinions. I'm sure that there is anybody more experienced in this matter. Regards, -- Jarek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB backup - the best way.
Dnia Wed, 28 May 2003 12:57:59 +0200 Jarek Jarzebowski [EMAIL PROTECTED] zezna/a co nastpuje: Hi, I have MySQL 4.0.12 working on Debian Linux box. DB server uses MYISAM and InnoDB tables. MySQL docs shows what is the best way to backup InnoDB tables but I don't want to shutdown db server every backup time. I suppose it is not a good idea to just copy database files and innodb log files to the safe place because of unwanted rollbacks danger. What if I use mysqldump to backup databases data, and then I copy innodb log files to the safe place? I suppose I should flush tables first. You can mysqldump InnoDB tables too. Copying InnoDB files (data or redologs) without shuting down mysql is a bad idea. You can also use mysql replication if you have spare server and do a cold backup from it. -- _/_/ _/_/_/ - Rafa Jank [EMAIL PROTECTED] - _/ _/ _/ _/ _/ Wirtualna Polska SA http://www.wp.pl _/_/_/_/ _/_/_/ul. Traugutta 115c, 80-237 Gdansk, tel/fax. (58)5215770 _/ _/ _/ ==* http://szukaj.wp.pl *==-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
