[BNM] Transferring 60GB of files from one server to another

[Alessandro De Maria]

On Wed, Dec 3, 2008 at 10:12 AM, David Pashley <david at davidpashley.com> wrote:
> On Dec 03, 2008 at 09:50, Alessandro De Maria praised the llamas by saying:
>> Well.. Have you ever used mysqldump on > 2 GB? If not good luck;)
>
> Yes, daily. Have three databases in the 20-30GB dump size. Data file is
> in the 110GB area.
>>

How long it takes to do a full backup (and restore)? I remember we had
to change from dump to hotcopy because we could not afford the risk of
spending several hours to recover.


>> The problems that are not solved by the --opt are:
>>
>> Still slooooower to Import than mysqlhotcopy
>> The size of the backup is a lot bigger. You would have to compress
>> (and decompress)
>> Importing from an older version can stop due to silly SQL errors and
>> would leave you with a big headacke.
>>
>> My database was 35 GB. mysqldump is just not meant to be used for
>> these sizes of DBs ;)
>>
> MySQL is not meant to be used with databases that size, but that's a
> different argument.
>
> Hmmm mysqlhotcopy is only meant to be used for MyISAM and ARCHIVE
> tables. Won't do InnoDB, which everyone should be using.

true, but what it is usually advised in situation like yours is to
have a Master InnoDB and a slave MyISAM, and then to backup from the
slave. This would allow you to have a shorted downtime and use
mysqlhotcopy.

But I guess it all depends on how critical the application is.

 http://dev.mysql.com/doc/refman/5.1/en/replication-solutions-backups.html


regards
Alex

>
> --
> David Pashley
> david at davidpashley.com
> Nihil curo de ista tua stulta superstitione.
> --
>
> BNM Subscribe/Unsubscribe:
> http://www.brightonnewmedia.org/options/bnmlist
>
> BNM powered by Wessex Networks:
> http://www.wessexnetworks.com
>



-- 
Alessandro De Maria
alessandro.demaria at gmail.com
Niccolo Machiavelli - Whosoever desires constant success must change
his conduct with the times.

Mobile: 0044 789 5092951