------_=_NextPart_001_01C671F3.23D14354
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

What are people doing for backups on very large MySQL/InnoDB databases?
Say for databases greater than 200 GB. Curious about the backup methods,
procedures, and frequency.

------_=_NextPart_001_01C671F3.23D14354--

--Sr1nOIr3CvdE5hEN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sunday, 7 May 2006 at 9:27:31 -0700, Robert DiFalco wrote:
A second question, but not for the first time: how would you *like* to
do backups if you had the choice? We're currently in the final stages
of the design of an online backup solution, and in the near future
I'll publish the specs. I won't mention them now to avoid influencing
you, but now's the time to speak up if you want something specific.

Greg
--
Greg Lehey, Senior Software Engineer
MySQL AB, http://www.mysql.com/
Echunga, South Australia
Phone: +61-8-8388-8286 Mobile: +61-418-838-708

Are you MySQL certified? http://www.mysql.com/certification/

--Sr1nOIr3CvdE5hEN
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFEXptrIubykFB6QiMRApHxAJ4xFlLUlzvwtZ7ZZp4Yvi +d00qTNgCdFN51
+Sd2nt87OX3G97SttQ77Npw=
=y35S
-----END PGP SIGNATURE-----

--Sr1nOIr3CvdE5hEN--

Fast, incremental, compressed, and no max-size limitations. Must be
transaction safe; able to run while transactions are going on without
including any started after the backup began; the usual stuff. =20

-----Original Message-----
From: Greg 'groggy' Lehey [mailto:grog (AT) mysql (DOT) com]=20
Sent: Sunday, May 07, 2006 6:14 PM
To: Robert DiFalco
Cc: mysql (AT) lists (DOT) mysql.com
Subject: Re: Backups with MySQL/InnoDB

On Sunday, 7 May 2006 at 9:27:31 -0700, Robert DiFalco wrote:
A second question, but not for the first time: how would you *like* to
do backups if you had the choice? We're currently in the final stages
of the design of an online backup solution, and in the near future I'll
publish the specs. I won't mention them now to avoid influencing you,
but now's the time to speak up if you want something specific.

Greg
--
Greg Lehey, Senior Software Engineer
MySQL AB, http://www.mysql.com/
Echunga, South Australia
Phone: +61-8-8388-8286 Mobile: +61-418-838-708

Are you MySQL certified? http://www.mysql.com/certification/


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3...ie.nctu.edu.tw

--byLs0wutDcxFdwtm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sunday, May 07, 2006 6:14 PM, Greg 'groggy' Lehey wrote:
On Monday, 8 May 2006 at 8:15:17 -0700, paul rivers wrote:
Yes, from an administrative perspective we're trying to make something
that feels "intuitive", and particularly the Microsoft approach seems
a good starting point for this aspect. If you have a pet feature not
discussed below, let me know.

On Sunday, May 07, 2006 9:30 PM, Robert DiFalco wrote:
We're certainly planning incremental backups, but they probably won't
be in the first release. We don't plan any size limitations (this is
a streaming backup), and it will be transaction-safe (statement-safe
for MyISAM) and online (i.e. concurrently with normal processing).

Compression is a different issue. We haven't considered it so far,
and though it's desirable, I don't see why we can't get an external
program to do this (bzip2 or gzip, for example; the choice depends on
your personal tradeoffs between time and space).

On Monday, 8 May 2006 at 15:55:07 -0300, Daniel da Veiga wrote:
The component we're working on at the moment is the streaming online
backup API. Basically you issue an SQL command BACKUP DATABASE, and
it outputs a data stream that you can point at your tape drive, to a
disk, or across the network to something like VERITAS. We're very
conscious of the multiple server issue, but it's going to have to wait
until we can back up one server properly. Dealing with replication is
a special case of multiple servers, so that will wait too. We will
backup the binlog, though, and our current thinking is to use it for
incremental backups, though this may change.

On Monday, 8 May 2006 at 16:09:23 -0500, Rich Duzenbury wrote:
This is also another aspect of the backup solution we're working on.
I'll put it down on the wish list.

On Tuesday, 9 May 2006 at 7:18:28 +1000, David Logan wrote:
I don't know Bacula, but I suppose I should investigate it. Do you
know anybody in the project?

Yes, this is very much the intention. It's the API that we're
defining now. We've been talking to Zmanda (http://www.zmanda.com/),
who are interested in extending amanda with MySQL plugins, and we'd be
more than happy for others to join in.

Yes, this is also on the horizon, and we're working on it.

Thanks to all of you for your input. I'll try to get more information
out for review in about 10 days.

Greg
--
Greg Lehey, Senior Software Engineer
MySQL AB, http://www.mysql.com/
Echunga, South Australia
Phone: +61-8-8388-8286 Mobile: +61-418-838-708

Are you MySQL certified? http://www.mysql.com/certification/

--byLs0wutDcxFdwtm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFEX+pEIubykFB6QiMRAjhbAJ9rUFK2idFHcm3Ih1MdT5 +d0nRThgCfaYHB
4sM08YRLsa3FxXLP8migjS0=
=dr4T
-----END PGP SIGNATURE-----

--byLs0wutDcxFdwtm--