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:
I'm curious if anyone has any thoughts on how I can handle a data
retention issue I've been facing with a larger dataset.
My process, roughtly is run mysqldump against the DB and gzip the
output. Then I transfer it off to a different machine for archival
onto optical media (yes I know
Hey all,
I'm curious if anyone has any thoughts on how I can handle a data
retention issue I've been facing with a larger dataset.
My process, roughtly is run mysqldump against the DB and gzip the
output. Then I transfer it off to a different machine for archival
onto optical media (yes
On 4/12/06, Tim Lucia [EMAIL PROTECTED] wrote:
Would you not lock tables on the slave? The idea of catching it up implies
this is way it is done. Catching up means once replication can proceed once
the tables are unlocked (on the slave).
At least that is the way I read it...
On the slave I
Jim wrote:
Hi All,
What is the standard procedure for mySQL backups.
We need to backup at least once a day on a windows OS.
Is there a SQL Server Job Agent type solution?
mysql has an implemented mysqldumper.
You could use that.
Ther are also some php dumper scripts and perl
On Tuesday, 11 April 2006 at 18:40:23 +1000, Jim wrote:
What is the standard procedure for mySQL backups.
We need to backup at least once a day on a windows OS.
Is there a SQL Server Job Agent type solution?
At the moment it's a mess. We're working on cleaning up the mess, and
you should see
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 4:05 AM
To: Jim
Cc: mysql@lists.mysql.com
Subject: Re: mySQL Backups
On Tuesday, 11 April 2006 at 18:40:23 +1000, Jim wrote:
What is the standard procedure for mySQL backups.
We need to backup at least once a day on a windows OS
the data be as portable as
necessary.
Just my $0.02.
J.R.
-Original Message-
From: Dana Diederich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 9:15 AM
To: Greg 'groggy' Lehey; Jim
Cc: mysql@lists.mysql.com
Subject: RE: mySQL Backups
We use a dedicated replicated instance
On 4/11/06, Dana Diederich [EMAIL PROTECTED] wrote:
We use a dedicated replicated instance for backups.
Every night, we lock all of the tables, and dump all of them to
compressed files, and unlock them afterwards. It takes a while to catch
up, but that doesn't hurt anything.
I too use this
:[EMAIL PROTECTED] On Behalf Of
Terry Burton
Sent: Tuesday, April 11, 2006 6:20 PM
To: mysql@lists.mysql.com
Subject: mySQL Backups
On 4/11/06, Dana Diederich [EMAIL PROTECTED] wrote:
We use a dedicated replicated instance for backups.
Every night, we lock all of the tables, and dump all of them
On 28 Jun 2003 at 10:12, Nils Valentin wrote:
I understood that the backup done by f.e mysqldump would dump the
create statement only for the index - not the actually data fo the
index. That would make the backup option create smaller files than
lets say if you copy it 1x1 on the OS command
-Original Message-
From: Keith C. Ivey [mailto:[EMAIL PROTECTED]
It's true that mysqldump doesn't put the data for the index itself
into the dump file. That does not automatically mean that the dump
files will be smaller than the .MYD, .MYI, and .frm files combined.
The dump
2003 7 1 04:11David Brodbeck :
-Original Message-
From: Keith C. Ivey [mailto:[EMAIL PROTECTED]
It's true that mysqldump doesn't put the data for the index itself
into the dump file. That does not automatically mean that the dump
files will be smaller than the .MYD, .MYI,
Yes, if you have transaction logging turned on.
You can edit the transaction log, and run it against the restored database.
Subhakar Burri wrote:
Can I roll forward if I do backups using Mysqldump? Say, I did backups using Mysqldump @ 8:00 AM and my instance crashed @ 2:00 PM. I can restore the
On Fri, Jun 27, 2003 at 08:08:40AM -0500, gerald_clark wrote:
Yes, if you have transaction logging turned on.
You can edit the transaction log, and run it against the restored database.
MyISAM doesn't have transactions.
Jeremy
--
Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine,
Ok, update log.
Jeremy Zawodny wrote:
On Fri, Jun 27, 2003 at 08:08:40AM -0500, gerald_clark wrote:
Yes, if you have transaction logging turned on.
You can edit the transaction log, and run it against the restored database.
MyISAM doesn't have transactions.
Jeremy
--
MySQL General
-Original Message-
From: Keith C. Ivey [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 5:49 PM
The dump file will be larger than the MyISAM data file for the
original table -- especially if you have many non-text columns
(dates, numbers, ENUM columns, etc.). In some
question of can I roll forward the changes to both table types ... Am I
missing something? Please clarify
SB
Original Message-
From: gerald_clark [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 11:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practices for mySQL Backups in Enterprise
Ok
On 27 Jun 2003 at 14:49, David Brodbeck wrote:
FWIW, if size is a problem, mysqldump files compress quite well with
gzip. (Lots of repeated text.) The same is true of update logs, if
you're keeping those.
The same is also true of the original tables (the .MYD files), so I
stand by my
Hi Gerald,
Do you know some good information about it, seems like I need to brush up a
bit on this.
I dont understand how you want to do a roll forward for a MySQL table -
especially if the backup is lets ay from 8 AM and the crash is at 2 PM.
Best regards
NIls Valentin
Tokyo/Japan
2003 6
. Ivey; [EMAIL PROTECTED]
Subject: Re: Best Practices for mySQL Backups in Enterprise
Hi Gerald,
Do you know some good information about it, seems like I need to brush up a
bit on this.
I dont understand how you want to do a roll forward for a MySQL table -
especially if the backup is lets ay
Hi Keith,
I understood that the backup done by f.e mysqldump would dump the create
statement only for the index - not the actually data fo the index. That would
make the backup option create smaller files than lets say if you copy it 1x1
on the OS command line basis f.e with cp.
This option
We are in the process of implementing enterprise wide (20,000+ users)
application that will use mySQL as the Database engine. I was wondering if
the slashdot readers can provide me some details about best practices /
experiences for Backing Up and Restoring mySQL Databases. I am planning to
setup
for mySQL Backups in Enterprise
We are in the process of implementing enterprise wide (20,000+ users)
application that will use mySQL as the Database engine. I was
wondering if
the slashdot readers can provide me some details about best
practices /
experiences for Backing Up and Restoring
If your tables are InnoDB, you could look at InnoDB HotBackup:
http://www.innodb.com/hotbackup.html
No I m not using InnoDB
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqlhotcopy does your locking for you.
SAQIB wrote:
We are in the process of implementing enterprise wide (20,000+ users)
application that will use mySQL as the Database engine. I was wondering if
the slashdot readers can provide me some details about best practices /
experiences for Backing Up
mysqlhotcopy does your locking for you.
So running
./mysqlhostcopy dbase /path/to/backup/dir
is perfectly safe while database operations (selct, insert, update etc)
are being performed?
---
Saqib Ali
http://www.xml-dev.com
--
MySQL General Mailing List
For list archives:
It is a perl program, so you can look at it and see.
SAQIB wrote:
mysqlhotcopy does your locking for you.
So running
./mysqlhostcopy dbase /path/to/backup/dir
is perfectly safe while database operations (selct, insert, update etc)
are being performed?
---
Saqib Ali
http://www.xml-dev.com
On 26 Jun 2003 at 12:24, SAQIB wrote:
mysqlhotcopy does your locking for you.
So running
./mysqlhostcopy dbase /path/to/backup/dir
is perfectly safe while database operations (selct, insert, update
etc) are being performed?
Yes, but the inserts and updates will all be blocked until
Is this better than using mysqldump?
Regards,
Jake Johnson
[EMAIL PROTECTED]
--
Plutoid - http://www.plutoid.com - Shop Plutoid for the best prices on
Rims, Car Audio, and Performance Parts.
On Thu, 26 Jun 2003, SAQIB wrote:
mysqldump creates text files containing insert statements that recreate a
table and repopulate it with data. They are somewhat portable across
database servers and human editable if necessary. They take up less space
than the original table because they do not contain indices (only the
Cool, Thanks a ton. I think I will stick with mysqldump for a while until
my tables get too large. Currently my backups only take a few seconds.
Regards,
Jake Johnson
[EMAIL PROTECTED]
--
Plutoid - http://www.plutoid.com - Shop
On 26 Jun 2003 at 17:16, Ware Adams wrote:
mysqldump creates text files containing insert statements that
recreate a table and repopulate it with data. They are somewhat
portable across database servers and human editable if necessary.
They take up less space than the original table because
: Re: Best Pratices for mySQL Backups in Enterprise
On 26 Jun 2003 at 17:16, Ware Adams wrote:
mysqldump creates text files containing insert statements that
recreate a table and repopulate it with data. They are somewhat
portable across database servers and human editable if necessary
I'd instead setup a 2nd backup server that's a slave to the master,
replicates all the time, keeps in sync.
At X time, stop replication/mysql, backup data to tape .. restart mysql
and it will catch up/re sync back to master..
On Thu, 26 Jun 2003, SAQIB wrote:
mysqlhotcopy does your locking
35 matches
Mail list logo
