Hi All,
Can you please suggest any good third party software for backup and restore
of mysql db.
Right now i am looking at ZMANDA. Has any one worked on this, and used for
their production db, please let me know how it is and can we use the same
for our production 24/7 mysql db.
regards
anandkl
Hi All !
I did mysqldump mydb -uroot -ppass --databases --add-locks
--allow-keywords --create-options --extended-insert --routines -r file.sql
and after that in MySQL Command Line Client source file.sql
After that my view was converted to an empty table.
What should I do to backup and
Hi All !
I did mysqldump mydb -uroot -ppass --databases --add-locks
--allow-keywords --create-options --extended-insert --routines -r file.sql
and after that in MySQL Command Line Client source file.sql
After that my view was converted to an empty table.
What should I do to backup and
Hello.
MyISAM table of about 1.8 GB it stops restoring with no error output.
It looks strange. Get the debug binary of mysql command line tool
and create a trace file to find out the place where if fails. See:
http://dev.mysql.com/doc/refman/5.0/en/debugging-client.html
Jose Maria de Dios
Gleb Paharenko [EMAIL PROTECTED] wrote on 01/18/2006 11:02:15
AM:
Hello.
MyISAM table of about 1.8 GB it stops restoring with no error output.
It looks strange. Get the debug binary of mysql command line tool
and create a trace file to find out the place where if fails. See:
I am trying to restore a backup on a two processor machine with a Debian
installation with 2.4 kernel and 2GB or RAM, but when it reaches a
MyISAM table of about 1.8 GB it stops restoring with no error output.
The MySQL version is Distrib 5.0.16.
I have tried to restore it in many other systems
Greetings.
I've just hit an interesting problem. Luckily I don't actually *need* to
restore from a backup right now - I'm just trying to create a database
dump to submit an unrelated bug report.
Anyway ...
I'm using the command:
mysqldump -K DATABASE_NAME db.sql -p
However when I create
Daniel Kasak wrote:
Greetings.
I've just hit an interesting problem. Luckily I don't actually *need* to
restore from a backup right now - I'm just trying to create a database
dump to submit an unrelated bug report.
Anyway ...
I'm using the command:
mysqldump -K DATABASE_NAME db.sql -p
i think you can use -K on your mysqldump and it'll put the hints in there
for the mysql command to use as well
- Original Message -
From: Daniel Kasak [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thursday, September 29, 2005 7:45 PM
Subject: Backup / Restore database with foreign
Michael Stassen wrote:
Before loading the file,
SET FOREIGN_KEY_CHECKS = 0;
after loading the file,
SET FOREIGN_KEY_CHECKS = 1;
That's it! Thanks :)
Even better, upgrade to a newer mysql (4.1.1+), where they are
automatically added to the dump file for you.
Not until the client
[EMAIL PROTECTED] wrote:
Hi,
Thank you for your reply. If I have the create table info in my
dump file, while doing the restore using mysql dbname dump.dmp, I am
getting errors like
mysql -uMNMSDBA -pMNMSDBA -f mnms
c:\progra~1\mitel\opsman~1\temp\almhist.dmp
ERROR 1050 at line 11: Table
Ligaya Turmelle wrote:
I'm a beginner - but can't you also use mysqlimport?
Not in the case when you have made a backup using mysqldump while using
the default options. mysqlimport is a front end for LOAD DATA INFILE
(http://dev.mysql.com/doc/mysql/en/LOAD_DATA.html)
It is usefule when you
it from backup file.
Thanks
Anil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 12:58 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: backup/restore
Hi,
Thank you for your reply. If I have
PROTECTED]
Subject: RE: backup/restore
Hi,
with which options of mysqldump you have taken backup. if you
use --add-drop-table option then it will add drop table statement in
dump
file. otherwise it wont add that statement and you will get that type of
errors.
if you didn't use that option then drop
-
From: Tom Crimmins [mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 10:55 AM
To: Lakshmi NarasimhaRao (WT01 - TELECOM SOLUTIONS)
Cc: mysql@lists.mysql.com
Subject: RE: backup/restore
[snip]
I am doing backup for tables using Mysqldump. But while doing the
restore I
am not able to do
]
Subject: RE: backup/restore
Hi,
Thank you for your reply. Even though I used the --add-drop-table
option, I am getting the error messages. Actually I am taking the backup
for a group of tables as following
D:\Code\OPS\6.9.1.12\NetMgmt\OPS_src\C_src\backupmnms\Debugmysqldump
-uMNMSDBA -p
MNMSDBA
Hi,
I am doing backup for tables using Mysqldump. But while doing the
restore I am not able to do that using the same Mysqldump. Could you
please help me in that.
For backup : using Mysqldump -databases db_name ---tables table1
table2 dump.dmp
For restore : used Mysqldump
[snip]
I am doing backup for tables using Mysqldump. But while doing the restore I
am not able to do that using the same Mysqldump. Could you please help me in
that.
[/snip]
mysqldump is not intended to be used for the restore.
You need to run the following:
mysql -D dbname mysqldumpfile
You
I'm a beginner - but can't you also use mysqlimport?
Respectfully,
Ligaya Turmelle
Tom Crimmins wrote:
[snip]
I am doing backup for tables using Mysqldump. But while doing the restore I
am not able to do that using the same Mysqldump. Could you please help me in
that.
[/snip]
mysqldump is not
,
Narasimha
-Original Message-
From: Tom Crimmins [mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 10:55 AM
To: Lakshmi NarasimhaRao (WT01 - TELECOM SOLUTIONS)
Cc: mysql@lists.mysql.com
Subject: RE: backup/restore
[snip]
I am doing backup for tables using Mysqldump. But while doing
with this as a
backup/restore methodology assuming we still do lock tables and use the
binary log. This approach does take some additional admin effort if we add
or drop tables.
and the backup takes a few
minutes to run in total.
I would be iterested if anyone on the list sees any issues with this as a
backup/restore methodology assuming we still do lock tables and use the
binary log. This approach does take some additional admin effort if we add
or drop tables.
--
Eric
: Innodb assertion failure after binary backup-restore
Thanks for your replies.
Now I have three ways to go
1. replication
2. innodb hot backup tool
3. Make sure that no one is writing in to the database and start
backup when modified db pages in BUFFER POOL AND MEMORY becomes zero
Hi!
- Original Message -
From: Sp.Raja [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, July 27, 2004 5:52 PM
Subject: Re: Innodb assertion failure after binary backup-restore
Thanks for your replies.
Now I have three ways to go
1. replication=20
2
after binary backup-restore
Hi List,
We are using 4.0.15a MySQL. We need to backup database at times and we
empl=
oy the following method
FLUSH TABLES WITH READ LOCK
tar -zcf backup.tar.gz ibdata1 ib_logfile0 ib_logfile1
UNLOCK TABLES
and restore is reverse. We cannot overwrite all
Hi,
I was able to solve this by calling sync command, as my previous mail say.
Do you mean to say this will not work regardless of the whether we sync or not?? which
implies binary backup/restore for innodb is impossible?? We actually started with
mysqldump for backup, but that was slow when we
assertion failure after binary backup-restore
Hi,
I was able to solve this by calling sync command, as my previous mail say.
Do you mean to say this will not work regardless of the whether we sync or
not?? which implies binary backup/restore for innodb is impossible?? We
actually started with mysqldump
In article [EMAIL PROTECTED],
Sp.Raja [EMAIL PROTECTED] writes:
Hi,
I was able to solve this by calling sync command, as my previous mail say.
Do you mean to say this will not work regardless of the whether we
sync or not??
If it happens to work, then only by incident. I wouldn't rely on
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Tue, Jul-27-2004 6:24 PM
Subject: Re: Innodb assertion failure after binary backup-restore
Hi!
sync will not help.
You can run SHOW INNODB STATUS\G to monitor when InnoDB has flushed its
buffer pool.
Best regards
failure after binary backup-restore
In some cases mysql crashes while restore is trying to destroy
persistent databases and mysql.err says
000121 21:02:23 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint
Matsunobu, Yoshinori [EMAIL PROTECTED] wrote:
I'd like to ask about backup/restore(roll forward recovery) solutions
using mysqldump and binary logs.
^[$B!^[(JVersion : 4.0.20
^[$B!^[(JUsing 1 database.(ex. sample1db)
^[$B!^[(JAll tables are InnoDB.
I'm considering the following
Hi List,
We are using 4.0.15a MySQL. We need to backup database at times and we employ the
following method
FLUSH TABLES WITH READ LOCK
tar -zcf backup.tar.gz ibdata1 ib_logfile0 ib_logfile1
UNLOCK TABLES
and restore is reverse. We cannot overwrite all databases, some of them needs to be
From: Sp.Raja [EMAIL PROTECTED]
To: '[EMAIL PROTECTED] ' [EMAIL PROTECTED]
Date: Fri, Jul-23-2004 7:13 PM
Subject: Innodb assertion failure after binary backup-restore
Hi List,
We are using 4.0.15a MySQL. We need to backup database at times and we
employ the following method
FLUSH
Hello.
I'd like to ask about backup/restore(roll forward recovery) solutions
using mysqldump and binary logs.
・瘢雹Version : 4.0.20
・瘢雹Using 1 database.(ex. sample1db)
・瘢雹All tables are InnoDB.
I'm considering the following s
Hi List,
I use 3 databases Current, Persistent-1 and Persistent-2. I would like to take backups
of Current as when and required and restore them as desired without affecting
Persistent-1 and Persistent-2.
Initially thought of using mysqldump for this, but was worried about the performance
(I
-
From: Sp.Raja [EMAIL PROTECTED]
To: mysql [EMAIL PROTECTED]
Sent: Friday, April 02, 2004 10:28 AM
Subject: Backup/Restore Procedures
Hi List,
I use 3 databases Current, Persistent-1 and Persistent-2. I would like to
take backups of Current as when and required and restore them as desired
without
Hello,
I have a version of MySQL on my server (mysql Worm 11.18 Distrib
3.23.56, for PC-linux (i686)) which I wish to transfer towards a more
recent server (mysql Ver 11.18 Distrib 3.23.58, for PC-linux (i686)). I
make a complete backup of the data with the following command:
mysqldump - U
DANIELE Paolo [EMAIL PROTECTED] wrote:
I have a version of MySQL on my server (mysql Worm 11.18 Distrib
3.23.56, for PC-linux (i686)) which I wish to transfer towards a more
recent server (mysql Ver 11.18 Distrib 3.23.58, for PC-linux (i686)). I
make a complete backup of the data with the
got this error...
Delete link points outside datafile at 0
and in another two tables i get this error...
Couldn't fix table with quick recovery: Found wrong number of deleted
records.
I am using MySQL 3.23.44 in WinXP.
Is there any problem in Backup / Restore or I am doing something wrong ?
Whats
I have a working server and a development server. From time to time
I'd like to refresh the content of my development server with what's
on my working server. So I take one of my regular backups, that I get
by doing mysqldump database dbbackupJuly1-02. Then I gzip this,
ftp it over to my
]
Sent: Monday, July 01, 2002 6:30 PM
Subject: Stupid backup/restore question
I have a working server and a development server. From time to time
I'd like to refresh the content of my development server with what's
on my working server. So I take one of my regular backups, that I get
by doing
*
-Original Message-
From: Jesse Sheidlower [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 11:30 AM
To: [EMAIL PROTECTED]
Subject: Stupid backup/restore question
I have a working server and a development server. From time to time
I'd like to refresh the content of my development
On 1 Jul 2002, at 12:30, Jesse Sheidlower wrote:
What should I be doing instead? The docs don't seem to specify this,
and there doesn't seem to be an ignore or replace option for the
mysql command. Do I actually have to drop all the tables on my
development box before loading in from the
On Mon, Jul 01, 2002 at 01:23:38PM -0400, Keith C. Ivey wrote:
On 1 Jul 2002, at 12:30, Jesse Sheidlower wrote:
What should I be doing instead? The docs don't seem to specify this,
and there doesn't seem to be an ignore or replace option for the
mysql command. Do I actually have to drop
I have a mysql database that I backed up by copying my /var directory to a cd
before I installed a new release of linux. How do I restore it on the new
system? Do I need to create the database in the new version of mysql first,
or just copy some files from the old data directory into the new
]
Sent: Tuesday, June 11, 2002 5:06 PM
Subject: newbie backup restore question
I have a mysql database that I backed up by copying my /var directory to a
cd
before I installed a new release of linux. How do I restore it on the new
system? Do I need to create the database in the new version
the update log is.
Currently it's in d:\mysql\bin
Pete
Original Message
Subject: RE: backup/restore of mysql
Date: Tue, 10 Jul 2001 17:48:31 +0100
From: Simon Green [EMAIL PROTECTED]
To: 'Pete Kuczynski' [EMAIL PROTECTED]
Hi Pete
To emable loffing use the --log option eg --log-update
Greg Cope wrote:
Pete Kuczynski wrote:
Hi,
I've posted this question before, and some were kind enough to respond
with suggestions to my question [replication], but I'm looking for
something more difinitave.
Background: I'm running a production mysql database/php4/Apache on a NT4
Hi,
I've posted this question before, and some were kind enough to respond
with suggestions to my question [replication], but I'm looking for
something more difinitave.
Background: I'm running a production mysql database/php4/Apache on a NT4
IBM Netfinity server [3500 records, growing by 100 a
Kuczynski [mailto:[EMAIL PROTECTED]]
Sent: 10 July 2001 16:00
To: [EMAIL PROTECTED]
Subject: backup/restore of mysql
Hi,
I've posted this question before, and some were kind enough to respond
with suggestions to my question [replication], but I'm looking for
something more difinitave.
Background: I'm
: Re: backup/restore of mysql
Hi,
do I need to generate these logs using the my.ini file on NT.
Pete
Simon Green wrote:
You can use update/bin_update logs.
Run these logs from the time of the last backup and it should take you DB
up
to date till the time in went down
Pete Kuczynski wrote:
Hi,
I've posted this question before, and some were kind enough to respond
with suggestions to my question [replication], but I'm looking for
something more difinitave.
Background: I'm running a production mysql database/php4/Apache on a NT4
IBM Netfinity server
Hello mysql,
Today I played a little bit with two different ways of backup -
first one is to use BACKUP TABLE (which works for myisam only) and
the second one is SAVE DATA/LOAD DATA.
In both cases if I'm not mistaken the file is wrote by mysqld server
so there is no communication
Hi!
At 05:44 PM 6/1/01 +0400, you wrote:
Hello mysql,
Today I played a little bit with two different ways of backup -
first one is to use BACKUP TABLE (which works for myisam only) and
the second one is SAVE DATA/LOAD DATA.
In both cases if I'm not mistaken the file is wrote by mysqld
The manual section on BACKUP does not state what locking behavior the command
has. Does it lock all the tables at once that you backup in one statement or
does it lock them one at a time?
I.e. if I run:
BACKUP foo.bar, foo.baz, foo.blah TO '/tmp/mysqlbackups/'
Will it lock all three tables
Nevermind. I see that the manual online has this information. Sigh. It
doesn't do what I want unfortunately.
Best,
Kyle
On Monday 29 January 2001 09:32, Kyle Hayes wrote:
The manual section on BACKUP does not state what locking behavior the
command has. Does it lock all the tables at
56 matches
Mail list logo
