I could swear I've used mysqlhotcopy for innodb in the past; but I could be mistaken.
You could also add a read only slave off of one of your master dbs that you periodically take offline and backup. For that matter, you could also take one of your master dbs offline periodically and back it up; depending on how your using it. Clint Twelve Horses Mobile Social Web Email Clinton Goudie-Nice Architect / Senior Software Engineer [EMAIL PROTECTED] Phone: +1.801.571.2665 ext 3264 Mobile: +1.801.915.0629 Fax: +1.801.571.2669 LinkedIn: http://www.linkedin.com/in/cgoudie Twelve Horses 13961 Minuteman Drive Suite 125 Draper, UT 84020 www.twelvehorses.com On Tue, 2008-04-15 at 12:29 +0200, Michael A. Toth wrote: > Hi Ask, > > On Tue, Apr 15, 2008 at 12:16 PM, Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote: > > > > InnoDB. > > Okay, thanks. > > > Because it won't lock on a high number of queries. Because it's much > > harder to corrupt when the server crashes. Because it's much easier to use > > the resources the box provides. Because it is easier to backup. > > I understand everything, except the latest. Easier to backup? How can > I backup easily a single 10+ GB data file? mysqlhotcopy works with > myisam tables only. innodbhotcopy is a commercial product. Should I > use LVM snapshot? > > Thanks, > Michael >
