Hello *,
My INNODB database has a size of 80GO. I've a replication setup on 3 slaves and
I backup my db from them.
If a problem occurs on the database, a recovery from a dump takes around 6H !
That's too long for us.
2 ideas :
1. Stop the slave and rsync the folder /var/lib/mysql
Am 14.08.2012 09:42, schrieb Bob Sauvage:
Hello *,
My INNODB database has a size of 80GO. I've a replication setup on 3 slaves
and I backup my db from them.
If a problem occurs on the database, a recovery from a dump takes around 6H !
That's too long for us.
2 ideas :
1. Stop
Hi,
Lately I got this messgae in my errorLog file, need more datails why the DB
was restarted!
120711 19:42:06 mysqld restarted
120711 19:42:06 [Warning] Asked for 196608 thread stack, but got 126976
120711 19:42:07 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery
Hi List
I have (had) a mysql database running on a linux server which crashed
and suffered e2fsck file system corruption. I applied the e2fsck
filesystem checker, which recovered what appears to be most of the
files comprising the data, storing them in the lost+found
directory. This looks
Hi all,
does anybody know where can I find a recent guide/information regarding
the licensing of data recovery environments with /MySQL Enterprise Server/?
Regards
Dimitre
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http
Hello!
I got all data files (ibdata1, ib_logfile, etc) recovevered from mine
old Debian 3.1 box (and i dont know MySQL version :( ). I want to get
that DB running again.
Can i copy these files to newer version of MySQL, and if i can - how?
Any commands, any parameters?
--
MySQL General Mailing
Hi Johny
Do you have the my.cnf configuration file ?? that can simplify things.
Carlos
On 1/20/2010 3:32 AM, Johny Brawo wrote:
Hello!
I got all data files (ibdata1, ib_logfile, etc) recovevered from mine
old Debian 3.1 box (and i dont know MySQL version :( ). I want to get
that DB running
Hi John,
The data files will give you some informations like log_file_size, mutliple
tablespace is being used or not. Although my.cnf can help you a lot. With
the above information, use it with newer version of mysql.
Krishna
On Wed, Jan 20, 2010 at 3:02 PM, Johny Brawo lydyh...@gmail.com
Hey everyone,
I just posted new blog post about an online training class I will be doing
January the 13th. This class will cover backups, recovery and disaster
planning. It is completely free with no strings attached. If you are
interested, take a look at the blog post here:
http://www.paragon
I have 2 - 5.0.51a mysql databases setup in a dual master scenario. A is
master of B and vise versa...
In Linux 2.6.26 (if that matters).
Everything is great while all is running normally. But, when I am
testing the system by creating disasterous scenarios, I find some
challenges I hope to get
Towey
-Original Message-
From: Bryan Cantwell [mailto:bcantw...@firescope.com]
Sent: Wednesday, October 07, 2009 10:47 AM
To: mysql@lists.mysql.com
Subject: Replication recovery
I have 2 - 5.0.51a mysql databases setup in a dual master scenario. A is
master of B and vise versa...
In Linux
recovery
I have 2 - 5.0.51a mysql databases setup in a dual master scenario. A is
master of B and vise versa...
In Linux 2.6.26 (if that matters).
Everything is great while all is running normally. But, when I am
testing the system by creating disasterous scenarios, I find some
challenges I hope to get
[mailto:bcantw...@firescope.com]
Sent: Wednesday, October 07, 2009 11:12 AM
To: Gavin Towey
Cc: mysql@lists.mysql.com
Subject: Re: Replication recovery
When only one machine dies I do send the new master position info to the
still running slave, and yes, it does the trick.
My main challenge is when
I actually get the feeling you are not connecting as root.
Try mysql -uroot -p test instead of just mysql test
Have a nice day,
- Martijn
On Wed, Aug 26, 2009 at 03:02, Joemysql@bluepolka.net wrote:
OK, thanks, that got me in. But upon inspection, the user.host
values do not look fouled
Step # 1 : Stop mysql service
# /etc/init.d/mysql stop
Step # 2: Start to MySQL server w/o password:
# mysqld_safe --skip-grant-tables
Step # 3: Connect to mysql server using mysql client:
# mysql -u root
Step # 4: Setup new MySQL root user password
mysql use mysql;
mysql update user set
We have an inaccessible MySQL v5.0.45 DB (w/Innodb) we really
need some help regaining access to. While attempting to
adjust/add remote user access, we accidentally did the
following:
use mysql;
update user set host = 'SomeBogusIP' where user = 'root';
Now, we can't get into the DB to
Hey Joe,
stop the server, start it with --skip-grant-tables, change the root
entry in mysql.user to your liking, and then restart the server
without --skip-grant-tables.
viola!
Walter
On Wed, Aug 26, 2009 at 02:12, Joemysql@bluepolka.net wrote:
We have an inaccessible MySQL v5.0.45 DB
You have to reset the permissions.
http://dev.mysql.com/doc/refman/5.0/en/resetting-permissions.html
Carlos
On 8/25/2009 7:12 PM, Joe wrote:
We have an inaccessible MySQL v5.0.45 DB (w/Innodb) we really
need some help regaining access to. While attempting to
adjust/add remote user access,
OK, thanks, that got me in. But upon inspection, the user.host
values do not look fouled up as I thought they were (it appears
the bogus update may have aborted). But my access problem
remains
If I start with --skip-grant-tables, 'show databases' shows all
DBs. But without that flag, I
On Wed, Aug 26, 2009 at 02:12, Joemysql@bluepolka.net
wrote:
We have an inaccessible MySQL v5.0.45 DB (w/Innodb) we
really need some help regaining access to. While attempting
to adjust/add remote user access, we accidentally did the
following:
use mysql;
update user set
When you are in without the flag , issue the following:
Select current_user();
It should return root.
Then do this:
Grant all privileges on *.* 'root'@'%' identified by 'letmein'
It should work If you did not mess too much with grant tables.
Claudio
Il giorno 26 ago, 2009 4:36 m., Todd Lyons
-
From: Gavin Towey [mailto:gto...@ffn.com]
Sent: Thursday, July 30, 2009 5:08 PM
To: Cantwell, Bryan; mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Hi Bryan,
Please define out of whack. Tell us exactly what you're doing when you
restart, and what the replication state
, Bryan [mailto:bcantw...@firescope.com]
Sent: Friday, July 31, 2009 10:08 AM
To: mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Before I simulate a total server failure, master1 is using binary file
msyql-bin1 position 2231467 and it's slave master2 is following the
correct
-
From: Gavin Towey [mailto:gto...@ffn.com]
Sent: Friday, July 31, 2009 1:21 PM
To: Cantwell, Bryan; mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Bryan,
How are you restarting mysql? In the case a master crashes, it's definitely
common for the slave to miss the fact
...@firescope.com]
Sent: Friday, July 31, 2009 12:51 PM
To: mysql@lists.mysql.com
Subject: RE: Replication recovery on restart
Yes I am trying to simulate total failure. In this test case I am using 2
Virtual Machines and I just kill one and then when it comes back I have the
challenge described
I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases
both replicating wonderfully. They are configured in a dual master scenario so
that one can take over for the other in my HA environment I've built. All is
working great until... If one or the other box reboots or
: Thursday, July 30, 2009 11:00 AM
To: mysql@lists.mysql.com
Subject: Replication recovery on restart
I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases
both replicating wonderfully. They are configured in a dual master scenario so
that one can take over for the other
A colleague had to kill a MySQL server (on RedHat Enterprise Linux 5)
because it had some problem shutting down. Later I launched it (with
`/usr/share/mysql/mysql.server start`). In its err log I saw the recovery
happen, apparently with a successful completion, and then the usual
`). In its err log I saw the recovery
happen, apparently with a successful completion, and then the usual
announcement that the server is listening on its socket --- which I had
taken to mean the server is ready to be used. Apparently that's not quite
right. After that, I find another series
phone: +1-914-784-6424 (IBM T/L 863-)
AOL Instant Messaging: M1k3Sprtzr
Michael Dykman mdyk...@gmail.com
06/12/09 11:25 AM
To
Mike Spreitzer/Watson/i...@ibmus
cc
mysql@lists.mysql.com
Subject
Re: Mysterious progress after recovery in MySQL Community Edition 5.1.34
It looks to me like you
: Mike Spreitzer/Watson/IBM
Office phone: +1-914-784-6424 (IBM T/L 863-)
AOL Instant Messaging: M1k3Sprtzr
Mike Spreitzer/Watson/i...@ibmus
06/12/09 11:50 AM
To
Michael Dykman mdyk...@gmail.com
cc
mysql@lists.mysql.com
Subject
Re: Mysterious progress after recovery in MySQL Community Edition
am not using replication) if necessary; is there a faster way to do that
than uninstall and reinstall?
Thanks,
Mike Spreitzer
Mike Spreitzer/Watson/i...@ibmus
06/12/09 12:57 PM
To
Michael Dykman mdyk...@gmail.com
cc
mysql@lists.mysql.com
Subject
Re: Mysterious progress after recovery
Is there anyway of doing what is described below with version 5 or will
I l have to wait for MySQL 6.0
PlanetMySQL Blog: MySQL 6.0 Feature #2: Online Backup
Alexander Nozdrin, Chuck Bell, Lars Thalmann, Peter Gulutzan, Rafal Somla
BACKUP DATABASE copies all data and metadata in
Quickly scanning this page, it doesn't seem to give syntax for an
incremental backup. I am hoping to be able to run something that dumps
only data changed since the last backup.
Rob Wultsch wrote:
On Wed, May 14, 2008 at 10:25 PM, John Comerford
[EMAIL PROTECTED] wrote:
2) Incremental
a lot of money to to be DBA's, and good
chunk of that is understanding disaster mitigation/recovery.
K.I.S.S.: words to live by.
--
Rob
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
of money to to be DBA's, and good
chunk of that is understanding disaster mitigation/recovery.
K.I.S.S.: words to live by.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi Folks,
I am fairly new to MySQL and I am going to be setting up a web site on a
third party hosting machine. I continuously hear horror stories about
machines/sites being hacked and databases being destroyed. Despite my
best efforts I am sure I have some security flaws in my site. What
On Wed, May 14, 2008 at 10:25 PM, John Comerford
[EMAIL PROTECTED] wrote:
2) Incremental Backups - say one every half hour, then a script to transfer
that to an off site machine that way I can get the DB back to within the
last good half hour...
I've got MySQL 5.0.55a running on a Windows XP system. All tables in the
active database on the system are innodb. The startup log says that innodb
recovery completed and that connections are available. Meanwhile, mysql is
writing to the hdd at around 2MB/sec according to process explorer.
I
Dear all,
our DB server crashed and when I try to start Mysql
/etc/init.d/mysql/start
I get these lins in my error log
060921 13:00:14 mysqld started
060921 13:00:14 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from
The error message says to go to
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html to learn
how to set the different recovery options for innodb.
On 9/21/06, Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] wrote:
Dear all,
our DB server crashed and when I try to start Mysql
/etc/init.d
Hello,
I have some question about InnoDB crash recovery.
Q: I understand transaction and write to disk sequence as following
figure. Is this correct?
w/
innodb_flush_log_at_trx_commit = 1
innodb_support_xa = on
sync_binlog = 1
skip-innodb_doublewrite
Dear all,
I've been testing our backup and recovery strategies here at work.
When dumping all the databases I'm using this command:
mysqldump --all-databases --force -u root -p -h 192.168.45.7 all.sql
When this command is run I receive these error messages:
mysqldump: mysqldump: Couldn't
Paul Nowosielski wrote:
Dear all,
I've been testing our backup and recovery strategies here at work.
When dumping all the databases I'm using this command:
mysqldump --all-databases --force -u root -p -h 192.168.45.7 all.sql
When this command is run I receive these error messages
On Thursday 25 May 2006 12:09, you wrote:
Paul Nowosielski wrote:
Dear all,
I've been testing our backup and recovery strategies here at work.
When dumping all the databases I'm using this command:
mysqldump --all-databases --force -u root -p -h 192.168.45.7 all.sql
When
Paul Nowosielski wrote:
On Thursday 25 May 2006 12:09, you wrote:
Paul Nowosielski wrote:
Dear all,
I've been testing our backup and recovery strategies here at work.
When dumping all the databases I'm using this command:
mysqldump --all-databases --force -u root -p -h 192.168.45.7
Nowosielski
Webmaster
office: 303.440.0666 ext 219
cel: 303.827.4257
On Thursday 25 May 2006 13:24, gerald_clark wrote:
Paul Nowosielski wrote:
On Thursday 25 May 2006 12:09, you wrote:
Paul Nowosielski wrote:
Dear all,
I've been testing our backup and recovery strategies here at work
Hello everyone,
Today a script killed a few InnoDB tables in my database. Although I have
backups (2 days old) I want to recover - if possible - a more current state of
my database. Is it possible to recover tables via the ib_logfileX files?
If i simply open the files with VIm I can see that
)
The ib_logfileX files are log files used by the innodb storage engine
mainly to rollback any uncommitted transactions so that the database
is in a consistent state after it recovers from a crash, so I don't
think you could use that file for recovery of lost data, and yes the
file is basically text
古雷 wrote:
Hello:
If I use Multiple-Master Replication with two mysql server, when one of them
goes down(disk crashed) must I shutdown the good one to recover the
Multiple-Master Replication ?
I think yes.
Depends on what you mean with recover the Multiple-Master Replication
Do you want to
in status of the failed
server from the point of failure to the point of recovery , so it all
depends on how up-to-date your data is on the failed server.. here are some
typical cases ..
1) you have everything intact ( data, bin logs, *.info files, etc ) then
just bring back the failed server
Thanks a lot. I'll try.
- Original Message -
From: Kishore Jalleda [EMAIL PROTECTED]
To: 古雷 [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Wednesday, March 29, 2006 11:53 PM
Subject: Re: Multiple-Master Replication recovery
any one of the servers could go down in many ways like
1
Hello:
If I use Multiple-Master Replication with two mysql server, when one of them
goes down(disk crashed) must I shutdown the good one to recover the
Multiple-Master Replication ?
regards,
gu lei
, 2006 7:56 PM
Subject:Re: question about recovery with binlog
Hello.
There a lot of different ways to perform this operation. See:
http://dev.mysql.com/doc/refman/5.0/en/replace-utility.html
man sed
man awk
wangxu wrote:
How to replace it?
--
MySQL General Mailing List
For list
Paharenko [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Monday, January 23, 2006 7:56 PM
Subject:Re: question about recovery with binlog
Hello.
There a lot of different ways to perform this operation. See:
http://dev.mysql.com/doc/refman/5.0/en/replace-utility.html
man sed
man awk
Hello.
There a lot of different ways to perform this operation. See:
http://dev.mysql.com/doc/refman/5.0/en/replace-utility.html
man sed
man awk
wangxu wrote:
How to replace it?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
How to replace it?
The output is a binary file.
- Original Message -
From: Gleb Paharenko [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, January 20, 2006 10:11 PM
Subject: Re: question about recovery with binlog
Hello.
Just a possible workaround - you can parse
Hello.
Just a possible workaround - you can parse the output of mysqlbinlog and
replace the buggy statement with the correct one.
wangxu wrote:
My mysql version is 5.0.16.
My problem is similar to the bug.
My sql mode is ANSI and TRADITIONAL
If mysql can't do recovery with mysqlbinlog
Mysqlbinlog throw out a error ERROR 1231 (42000) at line 10: Variable
'sql_mode' can't be set to the value of '501481487' when i recovery a binlog.
What can i do?
:
Mysqlbinlog throw out a error ERROR 1231 (42000) at line 10: Variable
'sql_mode' can't be set to the value of '501481487' when i recovery a
binlog.
What can i do?
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http
My mysql version is 5.0.16.
My problem is similar to the bug.
My sql mode is ANSI and TRADITIONAL
If mysql can't do recovery with mysqlbinlog at my sql mode until the bug will
be fixed?
Follow is the information of my binlog
Hello.
If default-character-set can't set in [client]?
The comprehensive explanations you will find at:
http://bugs.mysql.com/bug.php?id=11673
wangxu [EMAIL PROTECTED] wrote:
Follow is a part of my my.ini.
PROTECTED] wrote:
I specifying Times for Recovery with mysqlbinlog.
Follow is my command:
mysqlbinlog --database=menagerie --stop-data=2005-11-14 9:22:01 C:\Program
Files\MySQL\MySQL Server 5.0\data\1.01 | mysql -uroot -p11 menagerie
Mysql server throw a exception:
mysqlbinlog
---
If default-character-set can't set in [client]?
- Original Message -
From: sheeri kritzer [EMAIL PROTECTED]
To: wangxu [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Friday, November 18, 2005 5:44 AM
Subject: Re: a question of specifying Times for Recovery
What does your my.cnf
such table properly, unless MYI (index) file
is written accordingly. Present recovery tools (myisamchk) are
normalizing database by index, so I cant just put there empty MYI file and
ask for recovery (then I will get empty table, basically). Is there any
recovery tool that restores MYI file by MYD
, unless MYI (index) file
is written accordingly. Present recovery tools (myisamchk) are
normalizing database by index, so I cant just put there empty MYI file and
ask for recovery (then I will get empty table, basically). Is there any
recovery tool that restores MYI file by MYD
Gleb Paharenko wrote:
Hello.
REPAIR TABLE ... USE_FRM helps in difficult cases. See:
http://dev.mysql.com/doc/mysql/en/repair-table.html
Thanks Gleb. I'd forgotten about that option.
To others who try the same thing - make sure you have enough space in your
TMPDIR or set
All,
I've got a table with about 25mill rows that was victim of a crash recently.
(power-failure).
I've been trying to recover it, but I'm not making much progress.
From the most recent attempts:
myisamchk --safe-recover --force table
- recovering (with keycache) MyISAM-table 'table'
Data
Per Jessen wrote:
I've got a backup of the table, but I'm not sure what sort of state
it is in.
Correction - no backup is available. This table has got to be recoverable.
--
/Per Jessen, Zürich
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
Hello.
REPAIR TABLE ... USE_FRM helps in difficult cases. See:
http://dev.mysql.com/doc/mysql/en/repair-table.html
Per Jessen [EMAIL PROTECTED] wrote:
All,
I've got a table with about 25mill rows that was victim of a crash recently.
(power-failure).
I've been trying to
try
REPAIR TABLE 'tablename'
Gleb Paharenko wrote:
Hello.
REPAIR TABLE ... USE_FRM helps in difficult cases. See:
http://dev.mysql.com/doc/mysql/en/repair-table.html
Per Jessen [EMAIL PROTECTED] wrote:
All,
I've got a table with about 25mill rows that was
We have a mysql cluster. I know we can make backup in the management server of
the mysql cluster with the command start backup.
After that, How we can make a point-in-time recovery ?
Example:
- I did a backup at 7:00am.
- at 11:00am I have a crash.
- I want to restore all my data until
: 1
MyISAM-table 'theTable' is corrupted
Fix it using switch -r or -o
Renato Golin wrote:
On Wednesday 06 April 2005 20:05, jon wrote:
Normal recovery seems to grab 490 rows... but, originally there were
some 22 million rows in there.
Seems your data file was corruped too not only the indexes
Hey folks...
While we weren't paying attention, one of the tables we were logging to
got big. Really big... like over 2 gigs... and then the server crashed
and the data became corrupt.
'Course, we'd like that data back...
Normal recovery seems to grab 490 rows... but, originally there were
On Wednesday 06 April 2005 20:05, jon wrote:
Normal recovery seems to grab 490 rows... but, originally there were
some 22 million rows in there.
Seems your data file was corruped too not only the indexes. and probably broke
when updating the 491st registry... try use myisamchk -e
-e
Hello,
I have a server here that ran MySQL 3.23.x
This box recently crashed as a result of a power outage (possible
surge, my surge protector may have failed)
The box doesn't boot up, but the HD is ok... all my docs are there..
So, I'm wondering if it's somehow possible to get the
[snip]
This box recently crashed as a result of a power outage (possible surge, my
surge protector may have failed)
The box doesn't boot up, but the HD is ok... all my docs are there..
So, I'm wondering if it's somehow possible to get the MySQL 3 files and
recreate them on another box we have
Thanks,
That was pretty easy...
And, thank you mysql!
;-)
Yves
On Fri, 28 Jan 2005 08:14:37 -0600, Tom Crimmins [EMAIL PROTECTED] wrote:
[snip]
This box recently crashed as a result of a power outage (possible surge, my
surge protector may have failed)
The box doesn't boot up, but
i use suse 9.0 and mysql 4.0 , i drop a db is very important for me ,
hoe to i can recover it ?do you have any tool for this function .
this is vital for me . please help me .
--
E.Norouzi
Site Administrative Of P.S.P.Co, Ltd.
Tel:+98-21-2865439/41
Fax:+98-21-2865120
International
Hi all.
My boss just pulled the power on our MySQL server.
Yes, I've already thanked him.
It's a 4.0.18 server, with MyISAM tables and InnoDB tables, running on
a 2.6.5 kernel and XFS filesystem.
The XFS recovery proceeded without any complaints.
The InnoDB recovery also seemed to go
On Thu, May 06, 2004 at 09:55:30AM +1000, Daniel Kasak wrote:
Hi all.
My boss just pulled the power on our MySQL server.
Yes, I've already thanked him.
It's a 4.0.18 server, with MyISAM tables and InnoDB tables, running on a
2.6.5 kernel and XFS filesystem.
The XFS recovery proceeded
Jeremy Zawodny wrote:
My question is: should I trust my data now?
Yes. InnoDB is fully ACID compliant.
So anyway, should I bother with a restore? What's the chance of having
data corrupted / missing after a power 'failure' and recovery as above
the old database onto a new server with only file access? The
documentation suggests to me that I need to copy all the *.frm, *.MYD, and *.MYI
files. If this is the case, where should I copy them to on the new server?
The technical director is away and I am in charge of this recovery... I dont
Hi,
I have recently had a system crash that required the
installation of a new hard drive. I have access to the
files on the old hard drive, on which is a database I
need to recover.
I am running MySql 3.23.37 and all the tables in the
database to be recovered are MyISAM.
How can I
Andy Hall [EMAIL PROTECTED] wrote on 07/04/2004 09:50:19:
Hi,
I have recently had a system crash that required the installation of
a new hard drive. I have access to the files on the old hard drive,
on which is a database I need to recover.
I am running MySql 3.23.37 and all the
Hi,
I have recently had a system crash that required the
installation of a new hard drive. I have access to the
files on the old hard drive, on which is a database I
need to recover.
I am running MySql 3.23.37 and all the tables in the
database to be recovered are MyISAM.
Hi,
I have recently had a system crash that required the
installation of a new hard drive. I have access to the
files on the old hard drive, on which is a database I
need to recover.
I am running MySql 3.23.37 and all the tables in the
database to be recovered are
Hi,
We have a (pre-existing) disaster recovery/backup script that uses =
mysqldump, ssh, mysql to backup an existing database. One of the tables =
is rather large (1 Gig or so), and the time that it takes to DROP =
TABLE on an already loaded recover server causes a timeout. I have =
confirmed
recovery/backup script that uses =
mysqldump, ssh, mysql to backup an existing database. One of the tables =
is rather large (1 Gig or so), and the time that it takes to DROP =
TABLE on an already loaded recover server causes a timeout. I have =
confirmed tested by creating an empty database
require the shutting down of the database (production). The shutting down of the
disaster recovery one isn't a problem... I may resort to it, but I'd prefer to just
figure out which timeout is causing the problem.
Thanks,
Steve Williams
-Original Message-
From: dan orlic [mailto:[EMAIL
.
The idea of doing the scp of the mysql data directory is not a bad
one, but would require the shutting down of the database (production).
The shutting down of the disaster recovery one isn't a problem... I may
resort to it, but I'd prefer to just figure out which timeout is causing
the problem
down of the disaster recovery one isn't a problem... I may
resort to it, but I'd prefer to just figure out which timeout is causing
the problem.
Thanks,
Steve Williams
-Original Message-
From: dan orlic [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 3:52 PM
To: Steve Williams
Cc
the scp of the mysql data directory is not a bad
one, but would require the shutting down of the database (production).
The shutting down of the disaster recovery one isn't a problem... I may
resort to it, but I'd prefer to just figure out which timeout is causing
the problem.
Thanks,
Steve Williams
Hi,
I have been backing up via the dubious method of copying the database data folder onto
another machine where it is properly backed up onto DLT.
(yes, I know I should have used mysqldump!)
Recovering some tables today I copied the files back into their position (including the ibdata1 file and
02, 2003 4:51 PM
To: [EMAIL PROTECTED]
Subject: mysql disaster recovery
Greetings Gurus,
I have a mysql server that I need to create a disaster recovery system
for. What I am planning on doing is putting the data dir on a NFS
mounted directory so that I can start mysql on either of two
Andrew,
Andrew Hall wrote:
John,
Thank you for your reply. I have read the replication chapter and this
seems to be easier, but I do have a few questions.
1. I am using InnoDB tables, at least there are innodb argument to
mysqld in the start script, so should I use mysqldump instead
:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 5:10 PM
To: halla3; mysql
Cc: John.Griffin
Subject: RE: mysql disaster recovery
Hi Andrew,
I am not a Guru. I would suggest that you look at MySQL's excellent
replication facility rather than NFS mount a drive. Having your data on
an NFS
: Wednesday 03 December 2003 22:47
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: mysql disaster recovery
This information may not be current, but I seem to remember hearing some
really nasty stories about people putting MySQL data dirs on NFS
exports. I would
Greetings Gurus,
I have a mysql server that I need to create a disaster recovery system
for. What I am planning on doing is putting the data dir on a NFS
mounted directory so that I can start mysql on either of two servers in
case one dies. The inbound connections would be load balanced
-
From: Andrew Hall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 4:51 PM
To: [EMAIL PROTECTED]
Subject: mysql disaster recovery
Greetings Gurus,
I have a mysql server that I need to create a disaster recovery system
for. What I am planning on doing is putting the data dir on a NFS
1 - 100 of 226 matches
Mail list logo
