Thank you Michael and Mathis! While we already knew about mysqlhotcopy, our tables are completely InnoDB-based, so this was not an option for us. Percona XtraBackup looks very good though. We will definitely give it a try. I just don't find any information on the website that it doesn't work with vanilla MySQL. Do you have any reference, Mathis?
Cheers, Colin Mathis Klooß <[email protected]> wrote: > Hi, > > mysqlhotcopy is a good idea but will not work with InnoDB, > when your using percona or mariadb you can use "Percona XtraBackup", > will not work with mysql (from oracle) > > http://www.percona.com/software/percona-xtrabackup > > best regards > Mathis Klooß > > Am 17.11.2013 08:36, schrieb Michael Fritscher: >> Hi, >> >> so the backup does need 2 hours? How big is our database?! Thats very, >> very long... >> A first idea would be mysqlhotcopy, which does the locking etc. for you - >> and copy the raw database files (instead of making sql-files which can >> take ages). Informations are under >> http://dev.mysql.com/doc/refman/5.1/en/mysqlhotcopy.html . It can do >> things e.g. skipping the index files which can be rebuilt, flush the logs >> etc. >> >> Another approach is using a lvm under the database-files. This way you >> get >> at least a consistent version which are on the HDDs. Yes, you loose all >> information which are only in the RAM, but that shouldn't be too much - >> und if you need to replay backups you loose always by average 12 hours - >> so 5-10 minutes more ore less aren't that important ;) >> >> Best regards, >> Michael Fritscher >> >> >> >> _______________________________________________ >> Ros-general mailing list >> [email protected] >> http://www.reactos.org/mailman/listinfo/ros-general > > > _______________________________________________ > Ros-general mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-general > _______________________________________________ Ros-general mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-general
