RE: use mysqldump and mysqlhotcopy together?

[Schwartz, Evelyn]

Hi,

I'm a relative newbie at MySQL (Oracle DBA implementing MySQL in a
production environment).  There does seem to be a lack of 'Best
Practice' documentation for MySQL in a production environment.

I opted for using both mysqldump and mysqlhotcopy.  Disk is cheap and
everything is automated so why not.  I have turned on the binary logs to
facilitate a point in time recovery.  As part of the mysqlhotcopy backup
I flush the logs and copy the previous days logs to another location.  I
figure that I will use the hot backup and the binary logs for any
disaster recovery and the dump for troubleshooting problems.

Evelyn

-Original Message-
From: Bing Du [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 10, 2004 11:50 AM
To: [EMAIL PROTECTED]
Subject: use mysqldump and mysqlhotcopy together?


Greetings,

I've been looking at the backup/recover related discussions in the list
archives for a while.  Seems to me most people use either mysqldump or
mysqlhotcopy.  We don't have a good MySQL backup scheme in place yet.
Now I have some questions based on my reading.

How do I know how each table was created if using mysqlhotcopy solely if
recovery needs to re-create the tables?  On the other side, my concern
about just using mysqldump is it may take long to backup and recover.
The size of all the databases we want to back up is about 5G.  We can
only allow the databases unavailable for access for a couple of minutes
at most if downtime can not be avoided completely.  So I'm thinking
about making use of both mysqldump and mysqlhotcopy together.  By that I
mean using mysqldump to dump table structures only (without any data)
once a week so I can know how the tables were created in the first place
and using mysqlhotcopy to backup actual database binary files every day.
How bad is my idea?

Thanks in advance for sharing experiences,


Bing

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: use mysqldump and mysqlhotcopy together?

[Kevin Carlson]

Bing Du wrote:

Greetings,

I've been looking at the backup/recover related discussions in the list
archives for a while.  Seems to me most people use either mysqldump or
mysqlhotcopy.  We don't have a good MySQL backup scheme in place yet.  Now
I have some questions based on my reading.
 

We use mysqldump and then a standard backup tool triggered by cron to 
backup the file it creates.  If you use mysqldump without the -d or -t 
flags, you will get the sql necessary to recreate the tables as well as 
the insert statements necessary to populate the tables.  For our 
particular application (which generates large amounts of DB reads and 
very few inserts/updates/deletes) we found that using mysqldump gave us 
an accurate snapshot of the data and was less to back up since the 
indexes in our case can get quite large.  We've been using that method 
for quite some time with good results.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]