2003年 7月 1日 火曜日 04:11、David 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 sma
> -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
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 comman
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 al
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 stat
> -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 som
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 lockin
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 beca
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 Plu
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
statements
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:
> > m
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 un
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
> 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: http://lists.mysql.
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
> 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]
; Subject: Best Pratices 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
> prac
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 a
18 matches
Mail list logo
