On Sat, Aug 02, 2008 at 09:01:26PM +0100, Magnus Manske wrote:
Knowing little about the current dump generation
process, but some
about terabyte-scale data handling (actually, we here are well into
the petabyte range by now;-), how about this:
* Set up the usual MySQL replication slave
* At one point in time, disconnect it from the MySQL master, but leave
it running in read-only mode
* Use that as the dump base
This should result in a single-point-in-time snapshot. Also, it will
reduce load to the rest of the system. Not sure if IDs will change
internally, though.
That's roughly equivalent to what Phil Greenspun says that the "SQL
studs" at Mass General Hospital do with their backups, though in their
case it's breaking a RAID mirror rather than a replication.
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra(a)baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates
http://baylink.pitas.com '87 e24
St Petersburg FL USA
http://photo.imageinc.us +1 727 647 1274
Those who cast the vote decide nothing.
Those who count the vote decide everything.
-- (Josef Stalin)